On Sat, Mar 22, 2008 at 3:06 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > * assign issues to 1.3.3 that are high priority and can be solved in > a timely manner > * assign all other issues to 1.4M1
* Reassign other new non-1.5 features to 2.0M1 (can be reassigned later) > * fix the 1.3.3 issues and release 1.3.3 > * when the release is approved, branch 1.3.x > * trunk is now Wicket 1.4 > * apply generics, flatten directory hierarchy, fix build scripts > * fix issues as we go along (if possible apply to 1.3.x) > * release 1.4-M1 > * fix the generics stuff issues discovered > * release 1.4-M2 > * go into release candidate mode > * release 1.4-rc1 until 1.4-rcx ... > * release 1.4 final > > In the mean time we could release 1.3.4, 1.3.5 if necessary. I'll make sure to release then in a steady pace. > There is one thing I'd like to extend our 1.4 release with: replacing > wicket.util.concurrent with the JDK API. This removes the additional > license burden and these classes. > > What goes into 1.4-M1? > - flattening of directory structure > - fixes to release script to accommodate for the flattening assign-to-me - Replace Enum with enum > What goes into 1.4-M2? I would say only one milestone release. If M2 is all about bug fixes, then it's more like a release candidate to me. So M1, rc.1, rc.n, final Frank
