[Cryptography-dev] Starting to think about release 0.2

[Paul Kehrer]

We’ve currently got the removal of asserts in the openssl backend tagged for 0.2. Do we want to move this back?  

There was also a fuzzer issue listed under the second release milestone that I moved to third.


On Tuesday, February 4, 2014 at 11:13 AM, Alex Gaynor wrote:

> Hey all,
>  
> David has conned me into volunteering to do our 0.2 release. Here are the things I see as high priority for this release:
>  
> * RSA/DSA primitive APIs
> * New random engine for OpenSSL
> * Re-adding CAST5
> * Making our release process include building wheels
>  
> My hope is that this is about 1-2 weeks of work, but we'll see, the scope of the assymetric work is a bit variable depending on format loading and passwords and such, so we'll see.  
>  
> If you think someone is missing from this, please mention it, and if you can add it to the 0.2 milestone on github.
>  
> Alex
>  
> --  
> "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
> "The people's good is the highest law." -- Cicero
> GPG Key fingerprint: 125F 5C67 DFE9 4084  
> _______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org (mailto:Cryptography-dev at python.org)
> https://mail.python.org/mailman/listinfo/cryptography-dev
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140204/d104aeea/attachment.html>