Creating a Release Candidate
The process should be much easier this time around now that XMLBeans is not in the incubator. Below is a list off the top of my head of things we need to do for making a release candidate 1 of 2.0.0 and 1.0.4 and 1.0.4-jdk1.3.
Let's shoot for getting the rc1 release out next week, on Feb. 2nd.
Checklist
(Check off the [] items with [X] as we complete them)
[X] Any remaining checkings go in now
[X](kkrouse) I know the XMLBean task and docs are out of date with respect to the command line tool
[X](kkrouse) Merge changes from branches/1.x into branches/1.x-jdk1.3 so they are in sync
[X](radup) Check in copy of jam src from codehaus
[X](yana) Remove jaxen download
[X](cezar) Rename (svn copy) the newstore2 package to store
[X](kkrouse) Check all version strings are correct in build files, docs, and source:
- I think we should append "-rc1" for each release candidate, so
- trunk version is 2.0.0-beta1
- branches/1.x is 1.0.4-rc1
- branches/1.x-jdk1.3 is 1.0.4-jdk1.3-rc1
- I think we should append "-rc1" for each release candidate, so
[X] Licensing issues for trunk:
[X](kkrouse) All our files should have Apache header
[X](kkrouse) External files should have a reference to the license
[X](radup) What's the license status of jsr173.jar? Is it possible to bundle?
[X](jacob) scrub test files. (Tests won't be bundled in src distribution, but we need the license anyway.)
- The branches/1.x and branches/1.x-jdk1.3 should be ok
[](takers?) Update docs:
[](straut) The docs/guide files
[X] README.txt, xkit/README, STATUS files
[X] Add a new CHANGES that lists all major changes and bug fixes
[X] CHANGES for branch/1.x and branch/1.x-jdk1.3
[X] (yana)CHANGES for trunk
- Maybe just "svn log" from last release?
- Or a bunch of one-liners? who made them, when, and a short description
[X](radup) Build the source and binary distribution on windows:
[X] smoke test it on both win/unix
[X] Check docs built with distribution are good (javadocs, guides, samples)
[X](radup) Post zip and tgz of release candidate on xmlbeans.apache.org/dist
[X](kkrouse) Send a [VOTE] email to dev list for making a release of all
We can still do bug fixes after the rc1 goes out. We'll just make an rc2, rc3, etc. Once the final rcX is good, we'll create a new branch named 2.0.0, redo the version string, and make a release of that.
Once the release checks out ok:
[] After vote is complete, sign the distribution
- See the Incubator project's docs on SigningReleases
- KEYS file in svn may need updating (all devs should add their pgp/gpg sigs to it)
[] Copy the release to /www/www.apache.org/dist/xmlbeans.
- Read the excellent docs: http://www.apache.org/dev/mirrors.html and http://www.apache.org/dev/mirror-step-by-step.html
- Also copy the xbean-X.Y.Z.jar to /www/www.apache.org/dist/java-repository/xmlbeans/jars so Maven users can download the jars.
[] Tag the release candidate in svn after all svn changes are complete. (eg., *svn copy -r 154376 https://svn.apache.org/repos/asf/xmlbeans/branches/1.x-jdk1.3
https://svn.apache.org/repos/asf/xmlbeans/tags/1.0.4-jdk1.3*
)
[] Update website version numbers, etc.
[] Email the dev and user list saying the rc has been released.
- Announce email sent to announce@apache.org must be sent from a @apache.org email address. Include short project description so folks on announce@apache.org mailing list can filter it out – it's a large list.