Well, Depending on the speed of incubation and our development efforts, I think we will do:
wicket-1.2.3 outside wicket-1.2.4 outside (bugfixes) wicket-1.3-alpha-incubating / wicket-2.0-alpha-incubating wicket-1.3-beta1-incubating / wicket-2.0-beta1-incubating wicket-1.3-beta2-incubating / wicket-2.0-beta2-incubating wicket-1.3-beta3-incubating / wicket-2.0-beta3-incubating wicket-1.3-rc1-incubating / wicket-2.0-rc1-incubating wicket-1.3-rc2-incubating / wicket-2.0-rc2-incubating graduation! wicket-1.3 / wicket-2.0 The number of releases of alhpa, beta and rc's can vary. We have a history of some pretty long beta/rc phases, so I think these can coincide with a pre-graduation schedule. I intend not to stay in the incubator too long. :-D As for the qualifications, I think that our beta's are pretty high ceremony, and the 2.0-alpha willl be also high ceremony, deserving an ASF incubator PMC vote and full release. It is my intention to get our IP problems out of the way ASAP using these releases and to have the ASF style releases in place before long. Martijn On 10/5/06, Upayavira <[EMAIL PROTECTED]> wrote:
Martijn Dashorst wrote: > All, > > We are currently working on fixing the last bugs in 1.2.3, and can > release (I think in about a week or two). This would mean that the > release would stem from inside the incubator, if we are not fast > enough. > > We need to get our release plan together for this release. I'm not > sure about what was said and possibly approved on doing such releases > whilst in the incubator. > > We have expressed our concerns regarding a wicket-incubator-1.2.3.zip > distribution. > > As such I'd like to propose the following. We roll our release from > the Apache svn repository, and use our current build process to > release the distributions. This means: > - we don't use the Apache brand (i.e. we don't release Apache Wicket, > but just Wicket) > - release it at sourceforge.net, and in ibiblio.org under wicket > - in readme and notice we mention that the project is in the > incubator, but that this release is not endorsed nor approved by the > ASF > > My reasons for doing it this way is that we: are too fresh inside the > incubator to hold back the release until all ASF criteria are met (our > users deserve this release asap). > > Does any one from our mentors care to elaborate? Martijn, Thanks for your explanations. I think it would actually be much easier to work out the best course if you could explain your intentions regarding releases that come after this one. Are you suggesting that you intend 1.2.3 to be the last in the 1.2.x line, and the next release will likely be (major bugs notwithstanding) 1.3-incubating? If you can give a flavour of that, I'm sure we can wrap this question up pretty straight-forwardly. Regards, Upayavira
-- <a href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a> for <a href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a> at the <a href="http://www.thebeststuffintheworld.com/";>Best Stuff in the World!</a>
