Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-29 Thread Michael Droettboom
On 05/29/2013 05:23 PM, Russell E. Owen wrote: > In article <51a51603.5030...@stsci.edu>, > Michael Droettboom > wrote: > >> I am going to hold off one more day on making the release candidate. >> There are three blocker bugs that were discovered over the weekend and >> I'd like to give them a

Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-29 Thread Russell E. Owen
In article <51a51603.5030...@stsci.edu>, Michael Droettboom wrote: > I am going to hold off one more day on making the release candidate. > There are three blocker bugs that were discovered over the weekend and > I'd like to give them a chance for review first:... Thanks for the update. T

Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-28 Thread Michael Droettboom
I am going to hold off one more day on making the release candidate. There are three blocker bugs that were discovered over the weekend and I'd like to give them a chance for review first: #854 and #2061: These both have to do with problems with ignoring limits and can be fixed by the same cha

Re: [matplotlib-devel] Closing in on 1.3.0 release candidate

2013-05-24 Thread Michael Droettboom
I've gone ahead and created the 1.3.x branch on master. This means that the feature freeze on master is effectively lifted. Any PRs for 1.3.x should be milestoned as such before merging (and can be merged to either master or the 1.3.x branch). That milestone will indicate to me what needs to