working on 1.3 means committing to wicket-1.x but if we do that now it means we have to branch wicket and have
wicket-1.x <-- head for 1.3
wicket-1.2.x <--- head for 1.2
because 1.x will have api breaks
if we do that _now_ we have to commit bug fixes for 1.2 into at least two, possibly three branches
trunk
wicket-1.x
wicket-1.2.x
this obviously sucks big time, having to commit into two branches is already a pain - having three will drive anyone insane
so what we should do is wait for a week and see if any serious bugs surface ( so far two have ) and fix them in the 1.x branch. after a week we can create the wicket-1.2.x and start using 1.x for 1.3 head. ( the branch that is there now will go away until this weekend )
the idea here is that hopefully in a week all major bugs in 1.2.2 will be found+fixed and the chances of having to tweak something in 1.2.x will be significantly reduced.
in order to ensure stability of 1.x NO NEW FEATURES SHOULD BE COMMITTED, ONLY BUG FIXES ARE ALLOWED
everyone agree? no work on 1.3 or new features for 1.2 for at least a week. if you got itchy fingers knock yourselves out on 2.0
i want to see some +1s here people!
-Igor
------------------------------------------------------------------------- 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
