On 11/7/06, Alan Canon <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
>So unless any of the non-versioned issues seem like they should go in,
>it's time to start the fun of the release process.
>Hen
Should I prepare a summary of the non-versioned issues?
Only if you think any should go in 1.1.
What else can I do to push the release process?
I did some work on it at the weekend - fixed the code to build under
1.3. I'm working on the changes.xml file (release notes), I'll have
that finished today.
Other things that jump to mind:
* We should create a pom.xml file (Maven-2 build). As long as the
parent gets deployed (cf: some other thread on commons-dev). Feel free
to take a stab at that - shouldn't be too hard as there are other
pom.xml's to (largely) copy.
* Update the site - this mostly means changing 1.0 for 1.1 if it
appears in the text, but any problems you can find/patch in the site
are good for now.
* Create a jardiff report - need to see what's changed API-wise and
add that to release notes.
* Build the ant dist and maven site and call a vote. I'll take care of
that once the other bits are done.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
