[Cryptography-dev] Release Cadences

[Terry Chia]

I have no particular preferences either way but I agree with Donald
that we have to figure out our backports policy. Another minor concern
is that we have to be more vigilant to ensure that we don't release
any partially done features which *might* happen given our preferences
to split up new features into smaller, more reviewable PRs.

On Tue, Apr 22, 2014 at 6:52 AM, Joe Riopel <goon12 at gmail.com> wrote:
> I'm not sure "setting" a cadence is the right idea, let the project grow its
> own.
>
> On Apr 21, 2014 6:46 PM, "Steve Klabnik" <steve at steveklabnik.com> wrote:
>>
>> I haven't contributed anything, so weigh my words appropriately, but
>> it seems like many big projects are doing a six week release cycle.
>> Ember.js being the latest. They've seen a lot of really good benefits
>> from doing so.
>> _______________________________________________
>> Cryptography-dev mailing list
>> Cryptography-dev at python.org
>> https://mail.python.org/mailman/listinfo/cryptography-dev
>
>
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev
>