Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Michael Droettboom
On 10/15/2012 12:52 PM, Eric Firing wrote: > On 2012/10/15 5:50 AM, Michael Droettboom wrote: >> Sorry to be jumping in on this late -- I didn't have a chance to catch >> up with this over the weekend. >> >> I think I generally side with Eric here -- the rc candidate cycle is >> intended to be quit

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Eric Firing
On 2012/10/15 5:50 AM, Michael Droettboom wrote: > Sorry to be jumping in on this late -- I didn't have a chance to catch > up with this over the weekend. > > I think I generally side with Eric here -- the rc candidate cycle is > intended to be quite conservative. Nelle's pull requests are very >

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Michael Droettboom
On 10/15/2012 08:11 AM, Phil Elson wrote: Firstly, I think you are right to bring this up Eric, we should all agree what the best course is to take, and then all work together to get us there with the least amount of disruption possible. > if we leave PEP8 out of v1.2.x, and decide that once i

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Michael Droettboom
Sorry to be jumping in on this late -- I didn't have a chance to catch up with this over the weekend. I think I generally side with Eric here -- the rc candidate cycle is intended to be quite conservative. Nelle's pull requests are very welcome improvements, but they are also quite large and I

[matplotlib-devel] 1.3+ Release schedule (was: strategy for 1.2.x, master, PEP8 changes)

2012-10-15 Thread Todd
On Mon, Oct 15, 2012 at 2:11 PM, Phil Elson wrote: >> if we leave PEP8 out of v1.2.x, and decide that once it is released, >> v1.2.x will be changed >> only if critical bugs are found, requiring a v1.2.1 release > > I agree. I think it is important here to be very clear about what > constitutes a

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Phil Elson
Firstly, I think you are right to bring this up Eric, we should all agree what the best course is to take, and then all work together to get us there with the least amount of disruption possible. > if we leave PEP8 out of v1.2.x, and decide that once it is released, v1.2.x will be changed > only i

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Benjamin Root
On Monday, October 15, 2012, Nelle Varoquaux wrote: > > > On 15 October 2012 04:49, Jae-Joon Lee > > > wrote: > >> I'd agree with Eric on most of his points. >> >> On Mon, Oct 15, 2012 at 5:22 AM, Eric Firing >> > >> wrote: >> > If some of the PEP8 commits include genuine bug-fixes that need to

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Damon McDougall
On Mon, Oct 15, 2012 at 8:59 AM, Nelle Varoquaux wrote: > > > On 15 October 2012 06:10, Eric Firing wrote: >> >> On 2012/10/14 12:44 PM, Damon McDougall wrote: >> > On Sun, Oct 14, 2012 at 9:22 PM, Eric Firing wrote: >> >> All, >> >> >> >> I think we are in a messy situation, and we need to reac

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Nelle Varoquaux
On 15 October 2012 04:49, Jae-Joon Lee wrote: > I'd agree with Eric on most of his points. > > On Mon, Oct 15, 2012 at 5:22 AM, Eric Firing wrote: > > If some of the PEP8 commits include genuine bug-fixes that need to be in > > v1.2.x, then these fixes should be made via PRs directly against v1.

Re: [matplotlib-devel] strategy for 1.2.x, master, PEP8 changes

2012-10-15 Thread Nelle Varoquaux
On 15 October 2012 06:10, Eric Firing wrote: > On 2012/10/14 12:44 PM, Damon McDougall wrote: > > On Sun, Oct 14, 2012 at 9:22 PM, Eric Firing wrote: > >> All, > >> > >> I think we are in a messy situation, and we need to reach some agreement > >> as to how to proceed. This has been discussed a