This marks the end for trunk (was: VOTE: New roadmap and desicion on the future of Wicket 2.0 branch)

[Martijn Dashorst <ma...@gmail.com>]

I think it is time to close the vote and count our blessings. As Al is
now under water, surfing or generally having a great time, I call the
vote.

7 +1 binding votes,

According to me we have 4 abstainees, and no non-binding votes.

This wraps it: we will drop the constructor change and migrate all
features of trunk to branch 1.x in 2 releases: everything non-Java 5
goes into 1.3 and java 5 specifics into 1.4

Martijn

On 3/18/07, Johan Compagner <jc...@gmail.com> wrote:
> +1
>
> i have the model done pretty much in my workspace. So that i can commit
> quickly
>
> johan
>
>
> On 3/15/07, Al Maw <wi...@almaw.com> wrote:
> >
> > There's been a lot of comment and discussion lately about the future
> > direction of Wicket, and the trunk/2.0 branch in particular.
> >
> > We've done some hard thinking and we now have a roadmap for the future.
> >
> > When          What
> > ====          ====
> > Now           Backport the Model refactor and other remaining non-JDK-5
> >                features from 2.0 to the 1.3.x branch.
> > Soon          Release a 1.3.0-beta to the community.
> > Soon          Release a 1.3.0-rc1. [2, 3, etc. if required]
> >
> > A bit later   Release a 1.3.0 final.
> >                Fork a 1.4.x branch from the 1.3.0 release.
> >                Apply generics and other JDK-5 features to 1.4.x branch.
> >                This will make 1.4.x look just like 2.0, but with the same
> >                constructor/add logic as 1.2.x/1.3.x currently have.
> >
> > "now" ~= right now.
> > "soon" ~= within a couple of weeks.
> > "A bit later" ~= within a month or so.
> >
> > We will discontinue support for 2.0 once we have branched 1.4.x and
> > added generics support into it, at which point the 2.0 branch will be
> > renamed in subversion and left to stagnate.
> >
> > As already thrashed out in various discussions, this will achieve the
> > following:
> >
> >   - Provide a migration path for 2.0 users within a month or so, so they
> >     are not left high and dry. 1.4.x will be basically the same as 2.0
> >     currently is, only with the constructor change backed out.
> >
> >   - Give us two branches that will be very similar apart from JDK 5
> >     features, and thus make it easy to back-port fixes/features from
> >     the 1.4 branch to the 1.3 branch.
> >
> >   - Give us a 1.3.0 beta that is feature-complete, and thus make
> >     upgrading from beta >> RC >> final releases trivial.
> >
> > Best regards,
> >
> > Al
> >
>


-- 
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

Re: This marks the end for trunk (was: VOTE: New roadmap and desicion on the future of Wicket 2.0 branch)

[Johan Compagner <jc...@gmail.com>]

Ok i just converted everything to the new repository structure.
I have to fix some unit test but then i can commit the model change.

johan

On 3/19/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> I think it is time to close the vote and count our blessings. As Al is
> now under water, surfing or generally having a great time, I call the
> vote.
>
> 7 +1 binding votes,
>
> According to me we have 4 abstainees, and no non-binding votes.
>
> This wraps it: we will drop the constructor change and migrate all
> features of trunk to branch 1.x in 2 releases: everything non-Java 5
> goes into 1.3 and java 5 specifics into 1.4
>
> Martijn
>
> On 3/18/07, Johan Compagner <jc...@gmail.com> wrote:
> > +1
> >
> > i have the model done pretty much in my workspace. So that i can commit
> > quickly
> >
> > johan
> >
> >
> > On 3/15/07, Al Maw <wi...@almaw.com> wrote:
> > >
> > > There's been a lot of comment and discussion lately about the future
> > > direction of Wicket, and the trunk/2.0 branch in particular.
> > >
> > > We've done some hard thinking and we now have a roadmap for the
> future.
> > >
> > > When          What
> > > ====          ====
> > > Now           Backport the Model refactor and other remaining
> non-JDK-5
> > >                features from 2.0 to the 1.3.x branch.
> > > Soon          Release a 1.3.0-beta to the community.
> > > Soon          Release a 1.3.0-rc1. [2, 3, etc. if required]
> > >
> > > A bit later   Release a 1.3.0 final.
> > >                Fork a 1.4.x branch from the 1.3.0 release.
> > >                Apply generics and other JDK-5 features to 1.4.xbranch.
> > >                This will make 1.4.x look just like 2.0, but with the
> same
> > >                constructor/add logic as 1.2.x/1.3.x currently have.
> > >
> > > "now" ~= right now.
> > > "soon" ~= within a couple of weeks.
> > > "A bit later" ~= within a month or so.
> > >
> > > We will discontinue support for 2.0 once we have branched 1.4.x and
> > > added generics support into it, at which point the 2.0 branch will be
> > > renamed in subversion and left to stagnate.
> > >
> > > As already thrashed out in various discussions, this will achieve the
> > > following:
> > >
> > >   - Provide a migration path for 2.0 users within a month or so, so
> they
> > >     are not left high and dry. 1.4.x will be basically the same as 2.0
> > >     currently is, only with the constructor change backed out.
> > >
> > >   - Give us two branches that will be very similar apart from JDK 5
> > >     features, and thus make it easy to back-port fixes/features from
> > >     the 1.4 branch to the 1.3 branch.
> > >
> > >   - Give us a 1.3.0 beta that is feature-complete, and thus make
> > >     upgrading from beta >> RC >> final releases trivial.
> > >
> > > Best regards,
> > >
> > > Al
> > >
> >
>
>
> --
> Learn Wicket at ApacheCon Europe: http://apachecon.com
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.5 will keep your server alive. Download Wicket now!
> http://wicketframework.org
>