Re: [matplotlib-devel] re lease schedule for next version

2012-02-26 Thread John Hunter
On Sun, Feb 26, 2012 at 6:16 PM, Mark Lawrence wrote: > On 25/02/2012 17:13, John Hunter wrote: > > > After we get the bugfix out I'd like to gear up for a major python3 > release. > > Huge +1. > > I understand that the majority of Python and hence matplotlib people > work on *nix boxes, so if you

Re: [matplotlib-devel] re lease schedule for next version

2012-02-26 Thread Mark Lawrence
On 25/02/2012 17:13, John Hunter wrote: > After we get the bugfix out I'd like to gear up for a major python3 release. Huge +1. I understand that the majority of Python and hence matplotlib people work on *nix boxes, so if you'd like a hand with testing, or anything else come to think of it, o

Re: [matplotlib-devel] re lease schedule for next version

2012-02-26 Thread John Hunter
On Sun, Feb 26, 2012 at 9:26 AM, Pierre Raybaut wrote: > I found out that a similar issue was reported for Spyder the same day > as this one... > > So I just posted something about this bug on PyQt mailing list: > http://www.riverbankcomputing.com/pipermail/pyqt/2012-February/031166.html > > I ad

Re: [matplotlib-devel] re lease schedule for next version

2012-02-26 Thread Pierre Raybaut
I found out that a similar issue was reported for Spyder the same day as this one... So I just posted something about this bug on PyQt mailing list: http://www.riverbankcomputing.com/pipermail/pyqt/2012-February/031166.html -Pierre Le 26 février 2012 12:23, Pierre Raybaut a écrit : > Le 25/02/2

Re: [matplotlib-devel] Matplotlib-devel Digest, Vol 69, Issue 5

2012-02-26 Thread David kaplan
Hi, I will be on vacation with limited email from February 18-25, 2012. Bonjour, Je serai en conge du 18 au 25 fevrier, 2012. Thanks, David -- Virtualization & Cloud Management Using Capacity Planning Cloud computing m

Re: [matplotlib-devel] re lease schedule for next version

2012-02-26 Thread Pierre Raybaut
Le 25/02/2012 22:59, John Hunter a écrit : On Sat, Feb 25, 2012 at 1:54 PM, Benjamin Root wrote: > >> > I would be interested in accelerating the schedule. Since this is a >> > bug-fix release and not a major release, we can presume the tree is >> > pretty stable. How about we a