Thanks Loic, that helps A LOT! I'm +1 on a semver or semver-ish policy. I don't have a favorite of the proposed. And I'm +-0 on changing e.g. 1.9 to 2.0 or whatever is required to match the new release policy.
/Markus On Tue, Jun 16, 2015 at 02:15:59PM +0700, Loïc Bistuer wrote:
I've attempted to summarize the history of this thread. Note that I marked as +1 any generally positive feedback towards a given proposal, please correct if you feel misrepresented. # First iteration: 1/ Release every 8 months (previously undefined). 2/ LTS every 3rd releases (previously undefined but effectively 1.8 is the 4th release after 1.4). Thanks to point 1/ it means one LTS release every two years. 3/ LTS releases are supported for 3 years (previously undefined). Combined with points 1/ and 2/ this gives us 1 year of support overlap between 2 LTS (currently we committed as an afterthought to 6 months overlap between 1.4 LTS and 1.8 LTS). Core +1: Tim, Marc, Markus, Collin, Aymeric, Loïc # Second iteration: 4/ Deprecation shims must appear in a LTS release before being dropped. So far this is the only real change in the policy, first iteration only adjusted and/or pinned variables. In practice, thanks to point 2/, this only requires one exception to our current policy: features deprecated in the release *immediately following* an LTS have to be supported for 1 extra release. (e.g 1.9 PendingDeprecationWarning, 2.0 PendingDeprecationWarning, 2.1 DeprecationWarning). In return this makes it easier for 3rd-party apps to straddle 2 LTS releases without writing their own shims (provided their code runs without deprecation warnings on the oldest LTS). Core +1: Collin, Carl, Tim, Anssi, Michael, Loïc Refs: - django-compat thread (https://groups.google.com/d/topic/django-developers/ASnZ5Uyol6Y/discussion) - Collin's proposal https://groups.google.com/d/msg/django-developers/MTvOPDNQXLI/hou67ofj3EYJ and the 7 following responses. # Third iteration: 5/ Switching to Semantic Versioning Donald mentioned SemVer on IRC a few days ago. Since then various proposal were made to reconcile it with our release policy. So far Collin, Carl, Loïc, Tim, and Josh have expressed positive feedback to various proposals in that direction but I don't think we have yet reached consensus on a specific one. Tim updated the Google doc to reflect my latest proposal, so including me that's 2 formal +1 for it, but I'd say we should wait for at least a couple more votes before taking it to the technical board. Refs: - http://semver.org/ - Carl's analysis https://groups.google.com/d/msg/django-developers/MTvOPDNQXLI/Ojov2QBROg8J - Ryan's proposals https://groups.google.com/d/msg/django-developers/MTvOPDNQXLI/lBLWrhKJ6DIJ - Loïc's proposal https://groups.google.com/d/msg/django-developers/MTvOPDNQXLI/y2QbPVzSs6cJ Cheers -- LoïcOn Jun 16, 2015, at 02:37, Aymeric Augustin <aymeric.augustin.2...@polytechnique.org> wrote: If we're approaching consensus, could a kind soul put together a final proposal and submit it to the technical board, along with the main arguments or alternatives? I'm finding it difficult to follow this 50-message thread... Thanks :-)-- 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/B8FE1DF4-1542-465B-B3DE-A7CA0DE5C3BB%40gmail.com. For more options, visit https://groups.google.com/d/optout.
-- -- 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/20150616124159.GF25232%40pyler.local. For more options, visit https://groups.google.com/d/optout.
pgpYsNc2aWalH.pgp
Description: PGP signature
