You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Eelco Hillenius <ee...@gmail.com> on 2007/12/15 19:03:01 UTC
when will we do a deprecation release?
Hi,
We should also do a deprecation release. We could make our first
'final' release this (1.3.0), and remove all the finals and
deprecations etc with 1.3.1. Or would you prefer something else?
Eelco
Re: when will we do a deprecation release?
Posted by Eelco Hillenius <ee...@gmail.com>.
On Dec 15, 2007 10:33 AM, Igor Vaynberg <ig...@gmail.com> wrote:
> i would prefer 1.3.0 to have all the deprecations removed
>
> release something like 1.3.0-compat with all deprecations and 1.3.0 without
Sounds good.
Eelco
Re: when will we do a deprecation release?
Posted by Johan Compagner <jc...@gmail.com>.
thats exactly what i said:
Tag it
remove deprications
And then tag it again. (so this is the real branch of 1.3.0)
johan
On Dec 16, 2007 5:32 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> no we dont do it now. when we are ready to release 1.3.0 we first tag
> it and build the -migrate release. then remove all the deprecations
> and built the final. makes sense?
>
> -igor
>
>
> On Dec 16, 2007 2:27 AM, Johan Compagner <jc...@gmail.com> wrote:
> > So we tag what we have now with deprications. Then remove all the
> > deprications then tag/branch again what than is the 1.3.x stream?
> >
> > Then everybody that upgrades has to compile first with the depricated
> > one? That should be told then very clearly because if somebody waits
> > until 1.3.1 and just targets that one then it is much harder and
> > easier to make mistakes. But i guess the only solution for that is
> > keep the deprications/finals until 1.4 but that clutters api for 1.3
> >
> >
> > On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > i would prefer 1.3.0 to have all the deprecations removed
> > >
> > > release something like 1.3.0-compat with all deprecations and 1.3.0without
> > >
> > > -igor
> > >
> > >
> > > On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com>
> wrote:
> > > > Hi,
> > > >
> > > > We should also do a deprecation release. We could make our first
> > > > 'final' release this (1.3.0), and remove all the finals and
> > > > deprecations etc with 1.3.1. Or would you prefer something else?
> > > >
> > > > Eelco
> > > >
> > >
> >
>
Re: when will we do a deprecation release?
Posted by Johan Compagner <jc...@gmail.com>.
+1
I am also in no hurry to remove everything.
Clean everything up for 1.4
On 12/29/07, Martijn Dashorst <ma...@gmail.com> wrote:
> It sounds confusing as hell for our users. They already are struggling with
> 2 versions of wicket on the classpath... I'd hate to see our mailinglist
> flooded with questions regarding classdefnotfound and classnotfound errors.
> So I'd just keep 1.3 with deprecations, and ship 1.4 without them. This
> gives folks enough time to migrate their app if they choose to.
>
> Martijn
>
> On Dec 16, 2007 5:32 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > no we dont do it now. when we are ready to release 1.3.0 we first tag
> > it and build the -migrate release. then remove all the deprecations
> > and built the final. makes sense?
> >
> > -igor
> >
> >
> > On Dec 16, 2007 2:27 AM, Johan Compagner <jc...@gmail.com> wrote:
> > > So we tag what we have now with deprications. Then remove all the
> > > deprications then tag/branch again what than is the 1.3.x stream?
> > >
> > > Then everybody that upgrades has to compile first with the depricated
> > > one? That should be told then very clearly because if somebody waits
> > > until 1.3.1 and just targets that one then it is much harder and
> > > easier to make mistakes. But i guess the only solution for that is
> > > keep the deprications/finals until 1.4 but that clutters api for 1.3
> > >
> > >
> > > On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > > i would prefer 1.3.0 to have all the deprecations removed
> > > >
> > > > release something like 1.3.0-compat with all deprecations and
> 1.3.0without
> > > >
> > > > -igor
> > > >
> > > >
> > > > On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com>
> > wrote:
> > > > > Hi,
> > > > >
> > > > > We should also do a deprecation release. We could make our first
> > > > > 'final' release this (1.3.0), and remove all the finals and
> > > > > deprecations etc with 1.3.1. Or would you prefer something else?
> > > > >
> > > > > Eelco
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-rc2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
>
Re: when will we do a deprecation release?
Posted by Martijn Dashorst <ma...@gmail.com>.
Also, the release manager needs to build two releases. One is already
difficult enough to get right, imagine what happens with two.
And what will we do with 1.3.1? Maintain two as well?
Martijn
On Dec 29, 2007 3:56 PM, Martijn Dashorst <ma...@gmail.com>
wrote:
> It sounds confusing as hell for our users. They already are struggling
> with 2 versions of wicket on the classpath... I'd hate to see our
> mailinglist flooded with questions regarding classdefnotfound and
> classnotfound errors.
> So I'd just keep 1.3 with deprecations, and ship 1.4 without them. This
> gives folks enough time to migrate their app if they choose to.
>
> Martijn
>
>
> On Dec 16, 2007 5:32 PM, Igor Vaynberg <ig...@gmail.com> wrote:
>
> > no we dont do it now. when we are ready to release 1.3.0 we first tag
> > it and build the -migrate release. then remove all the deprecations
> > and built the final. makes sense?
> >
> > -igor
> >
> >
> > On Dec 16, 2007 2:27 AM, Johan Compagner <jc...@gmail.com> wrote:
> > > So we tag what we have now with deprications. Then remove all the
> > > deprications then tag/branch again what than is the 1.3.x stream?
> > >
> > > Then everybody that upgrades has to compile first with the depricated
> > > one? That should be told then very clearly because if somebody waits
> > > until 1.3.1 and just targets that one then it is much harder and
> > > easier to make mistakes. But i guess the only solution for that is
> > > keep the deprications/finals until 1.4 but that clutters api for 1.3
> > >
> > >
> > > On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > > i would prefer 1.3.0 to have all the deprecations removed
> > > >
> > > > release something like 1.3.0-compat with all deprecations and 1.3.0without
> > > >
> > > > -igor
> > > >
> > > >
> > > > On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com>
> > wrote:
> > > > > Hi,
> > > > >
> > > > > We should also do a deprecation release. We could make our first
> > > > > 'final' release this (1.3.0), and remove all the finals and
> > > > > deprecations etc with 1.3.1. Or would you prefer something else?
> > > > >
> > > > > Eelco
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Buy Wicket in Action: http://manning.com/dashorst
> Apache Wicket 1.3.0-rc2 is released
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
Re: when will we do a deprecation release?
Posted by Martijn Dashorst <ma...@gmail.com>.
It sounds confusing as hell for our users. They already are struggling with
2 versions of wicket on the classpath... I'd hate to see our mailinglist
flooded with questions regarding classdefnotfound and classnotfound errors.
So I'd just keep 1.3 with deprecations, and ship 1.4 without them. This
gives folks enough time to migrate their app if they choose to.
Martijn
On Dec 16, 2007 5:32 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> no we dont do it now. when we are ready to release 1.3.0 we first tag
> it and build the -migrate release. then remove all the deprecations
> and built the final. makes sense?
>
> -igor
>
>
> On Dec 16, 2007 2:27 AM, Johan Compagner <jc...@gmail.com> wrote:
> > So we tag what we have now with deprications. Then remove all the
> > deprications then tag/branch again what than is the 1.3.x stream?
> >
> > Then everybody that upgrades has to compile first with the depricated
> > one? That should be told then very clearly because if somebody waits
> > until 1.3.1 and just targets that one then it is much harder and
> > easier to make mistakes. But i guess the only solution for that is
> > keep the deprications/finals until 1.4 but that clutters api for 1.3
> >
> >
> > On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > i would prefer 1.3.0 to have all the deprecations removed
> > >
> > > release something like 1.3.0-compat with all deprecations and 1.3.0without
> > >
> > > -igor
> > >
> > >
> > > On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com>
> wrote:
> > > > Hi,
> > > >
> > > > We should also do a deprecation release. We could make our first
> > > > 'final' release this (1.3.0), and remove all the finals and
> > > > deprecations etc with 1.3.1. Or would you prefer something else?
> > > >
> > > > Eelco
> > > >
> > >
> >
>
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-rc2 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-rc1/
Re: when will we do a deprecation release?
Posted by Igor Vaynberg <ig...@gmail.com>.
no we dont do it now. when we are ready to release 1.3.0 we first tag
it and build the -migrate release. then remove all the deprecations
and built the final. makes sense?
-igor
On Dec 16, 2007 2:27 AM, Johan Compagner <jc...@gmail.com> wrote:
> So we tag what we have now with deprications. Then remove all the
> deprications then tag/branch again what than is the 1.3.x stream?
>
> Then everybody that upgrades has to compile first with the depricated
> one? That should be told then very clearly because if somebody waits
> until 1.3.1 and just targets that one then it is much harder and
> easier to make mistakes. But i guess the only solution for that is
> keep the deprications/finals until 1.4 but that clutters api for 1.3
>
>
> On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > i would prefer 1.3.0 to have all the deprecations removed
> >
> > release something like 1.3.0-compat with all deprecations and 1.3.0 without
> >
> > -igor
> >
> >
> > On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com> wrote:
> > > Hi,
> > >
> > > We should also do a deprecation release. We could make our first
> > > 'final' release this (1.3.0), and remove all the finals and
> > > deprecations etc with 1.3.1. Or would you prefer something else?
> > >
> > > Eelco
> > >
> >
>
Re: when will we do a deprecation release?
Posted by Johan Compagner <jc...@gmail.com>.
So we tag what we have now with deprications. Then remove all the
deprications then tag/branch again what than is the 1.3.x stream?
Then everybody that upgrades has to compile first with the depricated
one? That should be told then very clearly because if somebody waits
until 1.3.1 and just targets that one then it is much harder and
easier to make mistakes. But i guess the only solution for that is
keep the deprications/finals until 1.4 but that clutters api for 1.3
On 12/15/07, Igor Vaynberg <ig...@gmail.com> wrote:
> i would prefer 1.3.0 to have all the deprecations removed
>
> release something like 1.3.0-compat with all deprecations and 1.3.0 without
>
> -igor
>
>
> On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com> wrote:
> > Hi,
> >
> > We should also do a deprecation release. We could make our first
> > 'final' release this (1.3.0), and remove all the finals and
> > deprecations etc with 1.3.1. Or would you prefer something else?
> >
> > Eelco
> >
>
Re: when will we do a deprecation release?
Posted by Igor Vaynberg <ig...@gmail.com>.
i would prefer 1.3.0 to have all the deprecations removed
release something like 1.3.0-compat with all deprecations and 1.3.0 without
-igor
On Dec 15, 2007 10:03 AM, Eelco Hillenius <ee...@gmail.com> wrote:
> Hi,
>
> We should also do a deprecation release. We could make our first
> 'final' release this (1.3.0), and remove all the finals and
> deprecations etc with 1.3.1. Or would you prefer something else?
>
> Eelco
>