[Seaside-dev] WADivTag >> #clear
jfitzell at gmail.com
Sun Jun 26 21:36:55 UTC 2011
Well, I meant: "Is it cool to deprecate something part way through the 3.0.x
series?" or should we always be deprecating at the beginning of a series? It
just occurred to me that you might deprecate a bunch of things in 3.0 and
then something else in, say, 3.0.7. When it turns out that there is no 3.0.8
and the next release ends up being 3.1, you want to delete all the
deprecations but there was only a very short warning for the one added in
I'm not arguing for any particular approach; just raising the question.
On Sun, Jun 26, 2011 at 8:31 PM, Johan Brichau <johan at inceptive.be> wrote:
> I think Julian meant deleting the one that are already deprecated in 3.0
> first before adding new deprecations.
> But is there a 3.1 branch?
> On 26 Jun 2011, at 12:53, Philippe Marschall wrote:
> > 2011/6/25 Julian Fitzell <jfitzell at gmail.com>:
> >> Should we do this in the 3.1 branch so we can delete all the existing
> >> deprecated methods before adding new ones?
> > I would say deprecate in 3.0 and delete in 3.1.
> > Cheers
> > Philippe
> > _______________________________________________
> > seaside-dev mailing list
> > seaside-dev at lists.squeakfoundation.org
> > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside-dev