Frank Bille wrote: > +1 > > Could it be an idea to create a "release" next to branches for the > branches/WICKET_1_2_2 instead?
I agree with this. Basically, while svn doesn't distinguish between a 'branch' and a 'tag', we can do so through naming conventions. We should have: /trunk <- 2.0 /branches/wicket-1.2 <- 1.2 /releases/wicket-1.2.0 /releases/wicket-1.2.1 /releases/wicket-1.2.2 the current /branches/wicket-1.2.1 could easily be svn moved into the /releases directory. Things such as ajax_tryout should really be named 'sandbox', as one of: /branches/sandbox-ajax_tryout or /sandbox/ajax_tryout Ideally, only live branches would be kept in /branches. So, given that 1.0 and 1.1 are dead, and presumably have been released, they can be svn removed (as all code and history is still available in svn via the /releases directory. That, I believe, would give the clarification that Martijn (welcome back from hols) is looking for. Upayavira ------------------------------------------------------------------------- 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
