Differences between revisions 38 and 39
Revision 38 as of 2011-12-19 14:54:16
Size: 3902
Editor: wentforgold
Comment:
Revision 39 as of 2011-12-19 22:11:50
Size: 3706
Editor: fx
Comment: remove sp@m
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
   * I think we should append "[[http://www.hepburnathepburn.com.au/|accommodation]]" for each release candidate, so    * I think we should append "-rc1" for each release candidate, so
Line 34: Line 34:
     a. Maybe just "[[http://www.bookkeeperaustralia.com/|bookkeeper]]" from last release?      a. Maybe just "svn log" from last release?
Line 38: Line 38:
   * [X] Check docs built with distribution are good (javadocs, guides, samples [[http://nofaxpayday-loans.com/|no fax payday loans]])    * [X] Check docs built with distribution are good (javadocs, guides, samples)
Line 40: Line 40:
 * [X](kkrouse) Send a [VOTE] email to [[http://www.dananghotelsvietnam.com/|danang hotels]] list for making a release of all  * [X](kkrouse) Send a [VOTE] email to dev list for making a release of all

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
      1. trunk version is 2.0.0-beta1

      2. branches/1.x is 1.0.4-rc1

      3. branches/1.x-jdk1.3 is 1.0.4-jdk1.3-rc1

  • [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:

ReleaseCandidateChecklist (last edited 2011-12-19 22:11:50 by fx)