Hi Matt, I was thinking about this too and it came up on IRC today. I think if we were to strictly go with something like semver, we'd end up with a numbering scheme like 2.0, 2.1 (LTS), 3.0, 4.0, 4.1 (LTS), 5.0, etc, because features can be removed in between LTSs (assuming they're marked as deprecated in the previous LTS).
Collin On Thursday, June 11, 2015 at 9:31:08 PM UTC-4, Matt Austin wrote: > > On 11 June 2015 at 01:37, Collin Anderson <cmawe...@gmail.com > <javascript:>> wrote: > > > > I'd propose something slightly different, that's very close to our > current > > deprecation timeline: > > 1.8 (LTS): No features dropped. > > 1.9: Dropped features deprecated in 1.5, 1.6, 1.7 > > 2.0: Dropped features deprecated in 1.8 > > 2.1 (LTS): No features dropped. > > 2.2: Dropped features deprecated in 1.9, 2.0 > > 2.3: Dropped features deprecated in 2.1 > > > > Seems to me features deprecated in an LTS are fair game to disappear in > the > > next LTS. This allows us to remove "dotted paths in reverse() and url()" > > because that's deprecated in 1.8. > > > > If we can guarantee compatibility between LTSs, I think that would be a > huge > > win, at the cost of extending the removal of some deprecated features by > one > > release (8 months). > > > > Hi everyone, > > Sorry to stick my nose in, but thought I might throw a potential > spanner-in-the works with this release discussion, in regard to > version naming. > > I understand that the current version system doesn't have too much > inherent meaning, and that 2.0 will come after 1.9 'just so we don't > stay on 1.x forever'. > > With a more structured release plan, and LTS releases, would it be > worth considering LTS releases as 'major' version numbers, with > regular releases and 'minor' version releases? It would be easier to > identify LTS releases at a glance, and might provide more meaning to > the versioning scheme? > > Feel free to shut this idea down if it's going to open a can-of-worms :) > > > Cheers, > > -- > Matt > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/43108c2b-e8f0-4d69-bb70-da3ac4c516ca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
