Hi Tim, What I mean is we could still make it easy to support both LTS releases, even if we drop features deprecated in 1.8 before the next LTS according to the normal release schedule. Right? Because apps wouldn't need to use those deprecated features to support both 1.8 and 2.1. We could drop them in 2.0 like normal?
I'm trying to lessen the increased maintenance burden of Loic's proposal while still making it possible to easily support both LTS releases. > For "maintenance costs" I am not worried about supported deprecated APIs in old releases, only how long they stay around in master as that could be a barrier to innovation. Right, so the cost would be an extra 8 months before removing features deprecated in 1.9 from master. Thanks, Collin On Wednesday, June 10, 2015 at 2:09:13 PM UTC-4, Tim Graham wrote: > > Collin, I'm not following your reasoning about why dropping features > deprecated in one LTS (e.g. 1.8) in the next LTS (e.g. 2.1; I think you > made a typo in your timeline putting it next to 2.0?) will make it possible > to easily support both LTS releases? That's the purpose of Loic's proposal > I believe. > > For "maintenance costs" I am not worried about supported deprecated APIs > in old releases, only how long they stay around in master as that could be > a barrier to innovation. > > On Wednesday, June 10, 2015 at 1:54:53 PM UTC-4, Collin Anderson wrote: >> >> On Friday, May 8, 2015 at 12:12:37 PM UTC-4, Carl Meyer wrote: >>> >>> And there is a significant added maintenance cost to my proposal >>> compared to yours. Dropping deprecated APIs in the release after an LTS >>> means we still have to support those APIs for three more years (possibly >>> for four or five years after they were first deprecated). Dropping them >>> _in_ the LTS release shortens that window drastically. >> >> >> If we release every 8 months, that means we normally support deprecated >> features for 2 years. If we maintained LTS compatibility, then, yes, that >> would mean "supporting" the APIs for more than 5 years after deprecation. >> But to be clear, most of that time it's only security support for those >> APIs, and the APIs are long gone from master. Right? >> >> Thanks, >> Collin >> >> >> On Wednesday, June 10, 2015 at 1:37:30 PM UTC-4, Collin Anderson wrote: >>> >>> Hi All, >>> >>> Here are some thoughts in reply to some of the comments in the >>> django-compat thread. I don't stick to the LTSs myself, but I've helped >>> maintain apps that have 1.4 compatibility. >>> >>> On Tuesday, June 9, 2015 at 7:05:45 PM UTC-4, Loïc Bistuer wrote: >>>> >>>> 1.8 (LTS): No features dropped. >>>> 1.9: Dropped features deprecated in 1.4, 1.5, 1.6, 1.7 >>>> 2.0: No features dropped. >>>> 2.1 (LTS): No features dropped. >>>> 2.2: Dropped features deprecated in 1.8, 1.9, 2.0 >>>> >>> >>> 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). >>> >>> Collin >>> >>> -- 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/512e9895-7216-4e0d-95dc-8c506c6646dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
