On 10 June 2012 20:42, Keshav Kini <keshav.k...@gmail.com> 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?This does not sound reasonable to me: when lots of release numbers are bumped up one cannot expect a release manager to look at every patch to see if some new deprecation warning is in there. John > > -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 -- 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
