matplotlib-devel Mailing List for matplotlib

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 changes
#2070: Incorrect bbox of text: This was another negative fallout from 
the refactor to have text pass the baseline coordinate to the backend by 
default.
#2072: PEP8 conformance test failing: This is due to an unexpected 
interaction between setuptools and Travis
There is an additional blocker bug:
#1719: pickling gridlines: I suspect this is just an 
environmental/installation issue on the part of the OP, so I'm confident 
moving forward without that resolved.
#2024: Update homepage image: I'll get to this later tonight or tomorrow 
as part of my customary release day documentation cleaning
Cheers,
Mike
On 05/24/2013 05:40 PM, Michael Droettboom wrote:
> 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 be on the v1.3.x branch before making the release candidate
> early next week.
>
> Mike
>
> On 05/24/2013 01:38 PM, Michael Droettboom wrote:
>> The 1.3.0 release candidate tagging is scheduled for this coming Monday,
>> May 27. Unfortunately, due to an oversight on my part, I forgot that is
>> a holiday, so I'm going to postpone it one day to Tuesday, May 28. I
>> will be hoping to tag the release by 23:00 UTC that day.
>>
>> I think we're in really good shape for this release, given all of the
>> great work solving and triaging bugs that's been going on since the
>> feature freeze.
>>
>> I think all of the blocker bugs (except possibly #2061) are really close
>> to being resolved. There are a number of issues tagged for 1.3.x that
>> may unfortunately need to get punted, but not a very large number.
>>
>> Question: Should I create a 1.3.x branch now? The upside of doing that
>> is that development of post-1.3.x things can continue on master until
>> Tuesday, of course, and I think the pool of 1.3.x things is small enough
>> for that to make sense. The downside, of course, is that any existing
>> pull requests against master will have to be manually merged to 1.3.x.
>> That shouldn't be a big deal, though, because we don't have too many of
>> them left and I can just pull the PR logs when I'm back at the office on
>> Tuesday to find out which ones need to be merged. Any objections to
>> creating the branch now?
>>
>> Mike
>>
>> ------------------------------------------------------------------------------
>> Try New Relic Now & We'll Send You this Cool Shirt
>> New Relic is the only SaaS-based application performance monitoring service
>> that delivers powerful full stack analytics. Optimize and monitor your
>> browser, app, & servers with just a few lines of code. Try New Relic
>> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel