There are a lot of questions in that one post...
I certainly don't think that the 1-year deprecation rule is an absolute
rule.
1) Fixing bugs doesn't require deprecation.
2) Obscure code which isn't documented (except perhaps in the
function/class itself), is not used in the Sage library, which hasn't
seen any non-trivial commits in years, which isn't mentioned on any Trac
ticket... can be removed without deprecation.
Conversely, the more something is documented or used in the Sage
library, the more a deprecation is warranted.
3) Since deprecation is really meant for *stable* releases, any features
merged since the last stable release can be removed freely.
4) The deprecation policy should *not* depend on who is the author of
the code. We should treat every contributor alike.
--
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.
