Re: [matplotlib-devel] Release planning/milestones

2015-02-17 Thread Todd
I wasn't referring to just the default colors, but the default style in general. Things like background, line thickness, padding, ticks, etc. I thought that there was agreement that the default matplotlib style is not optimal, and that the point of the 2.0 release was to put all the stylistic chan

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Eric Firing
On 2015/02/08 12:05 PM, Thomas Caswell wrote: > The goal of pulling pyplot out of backend_bases is exactly that, to be > able to do everything using the OO interface in a convenient way. > https://github.com/matplotlib/matplotlib/pull/4082 The above PR is an illustration of one approach to making

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Thomas Caswell
To overhauling all of the default colors, I think that is still in the cards, but some one who is not me needs to drive that. The goal of pulling pyplot out of backend_bases is exactly that, to be able to do everything using the OO interface in a convenient way. Tom On Sun Feb 08 2015 at 4:50:51

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Todd
On Feb 8, 2015 1:13 AM, "Thomas Caswell" wrote: > > Hey all, > > To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If we want to do other breaking c

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Thomas Caswell
Ah, no I mean the exact opposite! My proposal is to cut 2.0 off of what ever the current stable release is (ex, 1.4.3) and then merge that into master. The next minor release would then be 2.1 and there would be no new 1.Y releases. Tom On Sun Feb 08 2015 at 2:04:24 PM Sandro Tosi wrote: >

Re: [matplotlib-devel] Release planning/milestones

2015-02-08 Thread Sandro Tosi
Hi all! On Sun, Feb 8, 2015 at 12:13 AM, Thomas Caswell wrote: > Hey all, > > To start with, the 2.0 release is pending a choice of new default color map. > I think that when we pick that we should cut 2.0 off of the last release and > then the next minor release turns into 2.1. If we want to do

[matplotlib-devel] Release planning/milestones

2015-02-07 Thread Thomas Caswell
Hey all, To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If we want to do other breaking changes we will just do a 3.0 when that happens. It make