[Jwebunit-development] It's alive!!! battleplan for release 1.2

[Martijn D. <ma...@da...>]

Contrary to popular believe, jWebUnit shows some signs of being alive.

Here's the plan as I see it:
- the list of developers is cleaned up, new active developers are enlisted
- we upgrade the dependend libraries to their latest released versions
- we make all tests pass, need to check the current tests, whether there 
are no false positives
- we close all patches which already have been committed to CVS
- we tag the repository with R1_2, perhaps even create a release branch 
(as is prescribed in 'Pragmatic version control')?
- we build a new release 1.2
- we release 1.2, and distribute it also to the maven repository 
(http://www.ibiblio.org/maven/jwebunit/jars) (need to figure out how to 
do that)

- we make a release plan for version 1.3

The timeschedule (my interpretation):
june 1 - administration of the developer list finished
june 2 - upgrades of the libraries commited in CVS, all tests pass
june 6 - tests are checked, all tests pass (no dummy tests)
june 7-10 - release preparation
june 10 - release of version 1.2
june 11 - attempt to upload jwebunit-1.2.jar to ibiblio
june 14 - battleplan for release 1.3 ready (which features go in, etc.)

Please feel free to comment on this plan.

With regards,

Martijn Dashorst