Status report on the release 1.2
- we close all patches which already have been committed to CVS Done.
- we tag the repository with R1_2, perhaps even create a release branch (as is prescribed in 'Pragmatic version control')?
Done.
- we build a new release 1.2 Done.
- we release 1.2, and distribute it also to the maven repository
Release 1.2 is released, announcement goes out tonight.
Maven release will follow later this week (I already figured out how to do it).
- 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
V - june 6 - tests are checked, all tests pass (no dummy tests)
V - june 7 - release preparation
V - june 13 - release of version 1.2
- - june 17 - attempt to upload jwebunit-1.2.jar to ibiblio
- - june 17 - battleplan for release 1.3 ready (which features go in, etc.)
Martijn Dashorst
------------------------------------------------------- This SF.Net email is sponsored by: GNOME Foundation Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event. GNOME Users and Developers European Conference, 28-30th June in Norway http://2004/guadec.org _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
