Instead of designing a process to ensure that the deprecation version is
absolutely correct we should spend some effort to timely review tickets :-P
On Sunday, June 10, 2012 8:42:05 PM UTC+1, Keshav Kini wrote:
>
> Volker Braun <vbraun.n...@gmail.com> writes:
> > The deprecation warning should include the Sage version where it was
> > deprecated, as in
> >
> > deprecation('foobar is deprecated', 'Sage Version 4.8')
>
> This means that the author of a patch needs to be able to know which
> version of Sage their patch will go into, i.e. if the release manager
> bumps the milestone on a ticket which introduces a deprecation warning,
> he should also change it back to needs_work. Yes?
>
> -Keshav
>
> ----
> Join us in #sagemath on irc.freenode.net !
>
>
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
