[Jwebunit-development] Status report release 1.2

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

Status report on the release 1.2

- the list of developers is cleaned up, new active developers are enlisted
Finished:
* Vivek Venugopalan
* Nick Neuberger
* Martijn Dashorst
are added as developers and Martijn Dashorst is added as admin. Old, 
inactive members have been removed.

- we upgrade the dependend libraries to their latest released versions
Finished. Is integrated into CVS - HEAD. Build using maven *and* ant 
both work with the new dependencies.

- we make all tests pass, need to check the current tests, whether there 
are no false positives
How far are we here? I got confirmation from Vivek that the cookie 
support *does* work, but that the PseudoServer doesn't support cookies. 
What should we do with the test?

- we close all patches which already have been committed to CVS
Jim is busy going through all past changes. How long do you need?

- we tag the repository with R1_2, perhaps even create a release branch 
(as is prescribed in 'Pragmatic version control')?
Not done yet.

- we build a new release 1.2
Not done yet.

- 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)
Not done yet.

- we make a release plan for version 1.3
Not done yet

The timeschedule (my interpretation):

Status   Date       Description
V      - june 1  -  administration of the developer list finished
V      - june 2  -  upgrades of the libraries commited in CVS, all tests 
pass
X      - june 6  -  tests are checked, all tests pass (no dummy tests)
X      - june 7  -  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.)

Time is running out for this schedule. I'll look into the tests tomorrow 
evening (girlfriend permitting). The release of june 10 is still possible.

Martijn Dashorst