On August 19, 2015 at 11:25:55 AM, Carl Meyer (c...@oddbird.net) wrote: > Hi Christian, > > On 08/18/2015 08:01 PM, Christian Hammond wrote: > > I know it's been a while since we discussed this, but today's security > > release is the first one that's really affecting our product and we've > > finally got things in shape to be able to start distributing unofficial > > Django security releases (we've also just been swamped since our > > discussion earlier this year). > > > > I wanted to dig into the versioning scheme just a bit. We tried going > > with local version identifiers, but it turns out these are fairly > > useless... > [snip] > > Given that, what would your feelings be on allowing for 1.6.11.x > > releases? This way we wouldn't take up any possible future versioning > > slots (unlikely as they may be), while being compatible with all > > versions of setuptools, and compatible with specifying version ranges. > > This would still appear solely on our own downloads page and > > announcements, with an appropriate note on them being unofficial builds. > > In my ideal world, the version number would help convey unofficial-ness > a bit more strongly, but after re-reading PEP 440 I don't think it > leaves us with any good options. I considered post-releases (e.g. > 1.6.11.post1), but "The use of post-releases to publish maintenance > releases containing actual bug fixes is strongly discouraged." So given > the lack of good options, I'm OK with 1.6.11.x. Anyone else on the core > team have a problem with that?
1.6.11.x should work fine, though I’m confused why not just issue 1.6.12+? > > > Also as a status update, we've started a fork and applied for the > > pre-notification list. I've backported all current security fixes to a > > branch, ensured the test suite passes with flying colors, and have added > > a README detailing everything you've requested. This is all up at > > https://github.com/beanbaginc/django. Let me know if there's anything > > you'd like changed. > > The README looks great, thanks! > > 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-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/55D49FEE.80503%40oddbird.net. > > For more options, visit https://groups.google.com/d/optout. > ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- 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/etPan.55d4a082.245ae313.6c62%40Draupnir.home. For more options, visit https://groups.google.com/d/optout.
