Volker raises some very practical points. Not sure I agree on breaking the laws of physics ;-)
Probably a lot of any given controversy on this would be to just add to the deprecation policy the following: "If you feel strongly that in a given instance this policy should not be followed, there should be a discussion on sage-devel about that specific functionality, with adequate time given and an attempt made to contact any known authors or users of the functionality." Naturally, I can already poke holes in this sentence I just wrote. So consider that a draft. But anyway I think that a lot of times what happens *in practice* is that so-and-so finds out about such a (possibly slight) exception to the policy on a ticket by chance and is annoyed, when doing some due diligence (often, unfortunately, requiring substantial Sage Trac knowledge) to find out who was responsible so that so-and-so was informed right away when it was proposed might have led to a good discussion. So at least encouraging wider discussion whenever this is violated would help - because most people won't care and will delete, and those who do care are at least somewhat more likely to see the discussion (though of course they may be on vacation, or away from Sage for a time, or whatever). - kcrisman -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
