[Cryptography-dev] Release Cadences

[Donald Stufft]

On Apr 21, 2014, at 2:31 PM, Paul Kehrer <paul.l.kehrer at gmail.com> wrote:

> Now that we’re an upstream dependency for at least one major project (PyOpenSSL) it might make sense to try to fall into a monthly release cadence. This way we wouldn't block important features in our bindings from being consumed by downstream and we’ll also be able to get features out more regularly in hazmat/recipes.
> 
> This would be helpful right now in allowing JP to schedule releases of PyOpenSSL that contain dependencies on new features we add. It would also help prevent situations like issue 941 (https://github.com/pyca/cryptography/issues/941) from arising in the future.
> 
> If we did want to do monthly release cadence then next Monday would be essentially a month from the release of 0.3. We would need to significantly triage our fourth release issue list (and get some reviews!), but that will always be true for any release.
> 
> Do people generally support this idea?
> 
> -Paul
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev



I think while we're still young, with new features being added at a high pace
that a monthly release cycle makes sense. I think we'll want to make sure that
this process is as automated as we can make it in order to reasonably achieve
that. Probably in the future we'll want to lengthen our release cadence but
that's a discussion for another day.

I do think that if we essentially say every X we'll issue a new release then
having release milestones don't really make a lot of sense though. If we're
doing time based releases then what gets released is whatever has landed by
the time the next release rolls around.

-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140421/900cf579/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140421/900cf579/attachment-0001.sig>