Creating a new GNU Classpath developer release snapshot.

Testing

Before starting on any release make sure at least the basic testing give OK results. After starting with the release branch you will have to do everything twice (head and release-branch). So don't create the branch too early.

Build Testing

Smoke Testing

Regression Testing

The autobuilder and regression tester on builder.classpath.org should have caught most issues, but it unfortunately does miss some things from time to time (hopefully the new Mauve framework from Tony will help here). So for now you need to install a <releasenumber>-1 first and run batch_run | tee old-results on it in mauve, then do that again against a CVS head version. Just diff -u old-results new-results and go through the changes to see if there are any regressions (search for ^+FAIL or ^-PASS to see if there are any suspicious entries).

Some programs come with regression suites themselves. If there is time it is a good idea to try a few like the jfree testsuite (that one is also a nice ant build and free swing test).

Bugs

Creating release branch

If the results of testing and the list of remaining bugs is manageable then start creating the release branch.

Make sure you have clearly marked your HEAD and release-branch working directories so you won't accidentally commit something to the wrong one.

Retesting and Last minute changes

Release

When there are no embarrassing bugs left we can start the actual release process.

Final changes

Building

Upload

The directive should look like:

 version: 1.1
 directory: classpath
 filename: classpath-<releasenumber>.tar.gz

Announce

Post-Release

ClasspathReleaseProcess (last edited 2009-02-05 23:51:59 by AndrewHughes)