On Fri, May 4, 2012 at 4:27 PM, tetsuo <[email protected]> wrote: > -1 RCx should only be used if you are pretty sure it could be released, > since it means *Release* Candidate.
Looking at Jira I don't see any reason why not to release it as 6.0.0 There are no planned API changes, new features, etc. Everything that I upgraded to 6.0-SNAPSHOT seems to work OK. I know of at least 15 users working with 6.0.0-beta1 and they don't experience any problems as well. > > > > On Fri, May 4, 2012 at 9:53 AM, Martijn Dashorst <[email protected] >> wrote: > >> I would opt for a beta2. IMO we should not make release candidates >> available for wider use, but really use release candidates as a way to >> push a release to its conclusion. I.E. each drop of a beta2 is a rc. >> >> Martijn >> >> On Thu, May 3, 2012 at 11:43 AM, Martijn Dashorst >> <[email protected]> wrote: >> > On Thu, May 3, 2012 at 10:44 AM, Emond Papegaaij >> > <[email protected]> wrote: >> >> I agree, it should be RC1, but first I want to merge my >> >> sandbox/atmosphere branch back in master and I think we should add >> >> wicket-cdi as experimental module as well, just as it is now. >> > >> > +1 >> > >> > Martijn >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
