> So the idea is that in Sage 4.0 we will drop all code that yields > DeprecationWarnings and has already been in Sage for at least 6 > months? I.e., we only purge deprecated code older than 6 months > during major releases, but not during point releases? > > I think a major release like 4.0 should (1) have reached some major > longterm milestones (e.g., Solaris port, 70% doctest coverage, etc.), > and also (2) be unusually rock solid. Deleting a bunch of code is > likely to cause subtle problems we don't think about, which conflicts > with (2). > I know that (2) is different than what most software projects do, > where their major new version releases are an unstable mess.
I agree with the goal of having a major release be rock solid. Maybe the right thing to do is to purge deprecated code in the next minor release (eg 4.1). Then if someone needs to get a good release that works with their old code, they can get the solid 4.0 release and use that forever. David --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
