All, We've discussed this over and over, and we keep running in circels, having the same conversation and arguments over and over.
This is how we're going to do it, it is a combination of the things that have passed. branches/wicket-1.x <- wicket 1.3 development after this weekend branches/wicket-1.2.x <- wicket 1.2 bug fixing after this weekend releases/wicket-1.2.2 <- wicket 1.2.2 release branch, which is 'read only' after delivery of wicket-1.2.2.zip tags/wicket-1.2.2 <- points to the branching point for the release tag, serves as patch base point If someone needs to build the wicket-1.2.2 release, then he needs to check out: releases/wicket-1.2.2 if someone needs to create a patch against 1.2.2, then he has to do so against tags/wicket-1.2.2 if we need a bug fix for 1.2.2, then it needs to go into branches/wicket-1.2.x, and possibly into branches/wicket-1.x and trunk I'm taking the whole sunday for this to 'restructure' the repo and build 1.2.2. If you have any outstanding changes for 1.2, then please get them into branches/WICKET_1_2, because after sunday this branch will be renamed branches/wicket-1.x Martijn -- Download Wicket 1.2.1 now! Embed Wicket components in your portals! -- http://wicketframework.org ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
