+1 -- Going with 1.8, 1.9, 1.10, 1.11 (LTS), 2.0 sounds like a solid plan. I don't think any of the (Pending)DeprecationWarnings are much of a public API. I've never seen them in the wild.
/Markus On Mon, Jun 22, 2015 at 11:20:52AM -0400, Michael Manfre wrote:
+1. I really don't like the idea of 2.x being odd. On Mon, Jun 22, 2015 at 10:33 AM, Loïc Bistuer <loic.bist...@gmail.com> wrote:Just when we thought we had a winner... I'd like to make a final proposal. Instead of delaying adoption of SemVer to 3.0 we could do so in 2.0 by introducing the 1.10 and 1.11LTS releases. The upside is that the new policy applies right away and we avoid the oddball 2.0 and 2.1 releases. It's much less invasive than the previous idea of renaming 1.9 to 2.0, but it still requires renaming PendingDeprecationWarnings in 1.8, and both warnings in 1.9. What do you think? -- Loïc > On Jun 17, 2015, at 08:47, Josh Smeaton <josh.smea...@gmail.com> wrote: > > I'm also +1 on the proposal as it stands, and neutral on when the semver versioning should begin. > > On Wednesday, 17 June 2015 05:03:47 UTC+10, Michael Manfre wrote: > I'm +1 on the Google doc proposal and like Markus, I support relabeling 1.9 to 2.0 to line the versions up with the new paradigm without the X.1 LTS oddball. > > Regards, > Michael Manfre > > On Tue, Jun 16, 2015 at 12:34 PM, Collin Anderson <cmawe...@gmail.com> wrote: > I also like the gdoc as it is. (1.8 LTS, 1.9, 2.0, 2.1 LTS, 3.0, 3.1, 3.2 LTS, 4.0, etc.) LTS is the final of a major version number, and we sacrifice a little bit of strict semver, but it give some nice meaning to the version numbers. > > > On Tuesday, June 16, 2015 at 12:22:44 PM UTC-4, Carl Meyer wrote: > Thanks Loïc, > > On 06/16/2015 01:15 AM, 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. > > > [snip] > > > > # 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 > > FWIW, I am also +1 on your proposal, as currently documented in the > Google doc. > > I was trying to come up with a proposal where LTS == major release for > the sake of argument, since it seemed like that was intuitive to at > least some people, but it's not worth the required lengthening of > deprecation paths. Your proposal is much better. (And it does make some > intuitive sense for the _last_ minor release in a major series to be LTS > rather than the first). > > Carl > > > -- > 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-develop...@googlegroups.com. > To post to this group, send email to django-d...@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/ebc7b0ae-27aa-4848-a6b5-9cec4b374895%40googlegroups.com . > > For more options, visit https://groups.google.com/d/optout. > > > > -- > GPG Fingerprint: 74DE D158 BAD0 EDF8 > keybase.io/manfre > > -- > 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/79aae5a5-58dd-4f05-a6dd-35685e06ebb5%40googlegroups.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/857E068D-347C-4C6A-8A1F-41569C3BC476%40gmail.com . For more options, visit https://groups.google.com/d/optout.-- GPG Fingerprint: 74DE D158 BAD0 EDF8 keybase.io/manfre -- 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/CAGdCwBu4CVmS3yGcmM9hW0-22Exfm5b72FVA2CQ_h9O_zTCrPQ%40mail.gmail.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/20150622171932.GB6715%40pyler.local. For more options, visit https://groups.google.com/d/optout.
pgpvtBirlnsZU.pgp
Description: PGP signature
