Hello,
Based on the feedback I received on when to cut the 1.4.8 and 1.4.9
releases I have decided to perform them now versus later.
I have created branches for each wicket version starting from 1.4.7
through 1.4.9.
1.4.7 line :
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.7
pom version is 1.4.7.1-SNAPSHOT (since 1.4.7 release is out)
1.4.8 line:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.8
pom version is 1.4.8-SNAPSHOT (will go to 1.4.8.1-SNAPSHOT once I cut
the 1.4.8 release)
1.4.9 line:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.9
pom version is 1.4.9-SNAPSHOT (will go to 1.4.9.1-SNAPSHOT once I cut
the 1.4.9 release)
I have moved trunk back to tracking the next wicket release 1.4-SNAPSHOT
and its version is now 1.4.10-SNAPSHOT
My plan is to always have the first release match the wicket version and
then any other releases use a fourth wicketstuff-core version number
starting from 1.
I plan on adding Hudson build jobs for each branch but right now my it
is only automatically building trunk so if anyone adds to one of the
branches and would like a snapshot build deployed into the maven
repository let me know.
I think a once a month release schedule for a branch is realistic
(especially since its unlikely many will have changes) but if you have
committed changes and need a non snapshot version let me know and I'll
see what I can do about creating a version.
I'll send another email when the 1.4.8 and 1.4.9 releases are staged to
vote on promoting them.
Regards,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
