On 3/22/08, Frank Bille <[EMAIL PROTECTED]> wrote: > > I think we might need another milestone to fix any API issues before > > going directly into RC mode. Think of it as the stable API milestone > > of Eclipse. > It doesn't make much sense to me, but I don't feel strongly about it > so if thats what we decide do, I don't object :-)
What doesn't make sense? M2 for API stability? RC's? Here's the Eclipse 3.4 plan: Milestone 1 (3.4 M1) - stable build Milestone 2 (3.4 M2) - stable build Milestone 3 (3.4 M3) - stable build Milestone 4 (3.4 M4) - stable build Milestone 5 (3.4 M5) - stable build Milestone 6 (3.4 M6) - stable build - API complete - API Freeze Milestone 7 (3.4 M7) - stable build- feature complete - development freeze - lock down and testing begins (May 2, 2008) Our target is to complete 3.4 in late June 2008. All official releases between M7 and 3.4 final are the release candidates. Though Eclipse does have nightlys, integration and other builds also. Martijn -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
