I know you guys really want to move on these releases and graduation, as do I. But I think it would look much better to the market if there was a final release of 1.3 ready as you graduate. I'd rather have people start using 1.3 out of the gates rather than 1.2.6, which I think will happen because most serious evaluations of the product for production usage will tend to use the non RC/BETA release of a product.
Just my two cents. -Craig Martijn Dashorst wrote: > > This is the proposal for our end game to a final release of Wicket 1.3.0 > > - build 1.3.0-beta 2 this weekend, release next week > - after the 20th start work on release candidates: > > These will not be official releases, because I want to move quickly on > these builds. So at least once every week we (I?) will publish a new > release on people.apache.org. We will hold a vote on whether the > released packages will be the final version, or a new release is > necessary. > > Schedule: > > 6/09 release beta 2 > 6/15 make beta 2 available for general public, if PPMC and IPMC don't > object > > 6/20 board@ meeting, graduate? > > 6/23 build rc1 > 6/26 vote: make rc1 final, or build a new one > > 6/30 build rc2 > 7/03 vote: make rc2 final, or build a new one > > 7/07 build rc3 > 7/10 vote: make rc3 final, or build a new one > > 7/14 give up > > Any one have other/better/alternative ideas? > > Martijn > > -- > Join the wicket community at irc.freenode.net: ##wicket > Wicket 1.2.6 contains a very important fix. Download Wicket now! > http://wicketframework.org > > -- View this message in context: http://www.nabble.com/-proposal--1.3.0-end-game-tf3883766.html#a11010154 Sent from the Wicket - Dev mailing list archive at Nabble.com.
