RomRaider

This thread will outline the steps to follow when releasing a new build of RomRaider. I handle all the builds right now, but in the future it may become someone else's job.

1. Ensure all file changes are checked in to SVN
2. Open project in NetBeans
3. Update version number and release date in ECUEditor.java and save
4. Commit ECUEditor.java to SVN
5. Build project and copy RomRaider.jar to dist directory
6. Download latest XML definitions from forum to dist directory
7. Get release notes.txt from SVN, make updates and save
8. Commit release notes and ECU definitions to SVN
9. If new graphics exist, get from SVN to dist directory
10. Compress files in to "RomRaiderx.x.x.zip", ensuring TortoiseSVN files are not present in archive
(Note: With version 0.3.2, we may be switching to an InstallJammer installer, which will make this step obsolete)
11. Post archive on forum, with relevent release notes quoted in post

Looks like these instructions are out of date.

Just a tad. At one point we were discussing an automated build process. I'll be doing a build here shortly to change the name and my environment isn't really set up anymore, so I think this is as good a time as any to define it. But I've never done it. Talk to me.

Sorry, but the next post to this thread scheduled for December 2008.

Coming in eight months early ...

The assembla repository that Paul (kascade) set up and has been using for test releases now has build automation using ant. There is still much to do, such as completing the centralization of version information, but I have push-button (a couple of clicks, actually) regeneration of everything, including installers and launchers. From clean source to both Windows and Linux installers in 76 seconds. I think it's coming along nicely.

As this seems to be the currently active fork, I'll keep working with Paul on enhancements and refinements. If anyone does pull the latest source to try it out, there is a file in the project's root directory, Building_RomRaider.txt, that gives brief instructions. Comments and suggestions welcome.


-- Steve