[Cryptography-dev] Release Cadences

[Alex Stapleton]

What's actually blocking us pushing a 0.4 master or 0.3.1 hotfix today?

I think a more structured release schedule could be a good thing but we 
need to figure out who we're doing it for and what our aims are clearly.


On 21 April 2014 19:31:37 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140421/1c6b75cc/attachment.html>