Re: [matplotlib-devel] Release Candidate

[Mark L. <bre...@ya...>]

On 10/09/2012 17:00, Michael Droettboom wrote:
> Today is the scheduled day for release candidate 1.2rc1.
>
> We seem to be in really good shape.  Thanks to everyone that has been
> working so hard to squash bugs, particularly ones that turned out to be
> bottomless rabbit holes.
>
> We have a few outstanding issues, which I'll categorize below:
>
> Critical things that need just a little more work:
>
> #1223    dpi= for bitmaps not handled correctly
> #1209    Pass linewidth to Mac context properly
> #786    savefig() renders paths and text differently than show()
> #113    dpi= doesn't seem to have any effect with MacOS X backend
>
> #1208    FAIL: matplotlib.tests.test_text.test_contains.test
> release_critical
> #1176    Reverted a previous change to artist transform setting. Fixes
> legend bug.
>
> Non-critical features that are near completion -- just needing some
> confirmation or testing:
>
> #847    Add stacked kwarg to hist and implement stacked hists for step
> histtype
> #751    Building on osx with python 3.2 OSX
>
> Problems requiring a fix in another project:
>
> #1126    Qt4 save dialog not functional on CentOS-5
>
> Things that are probably too big to fix now, but deserve warnings in the
> release notes:
>
> #854    Bug in Axes.relim when the first line is y_isdata=False and
> possible fix
> #740    plt.pcolormesh and shape mismatch
> #162    twinx and plot_date confirmed
>
> Reminders for the release manager:
>
> #1207    Add contributor and git stats to documentation
> #1070    Use github for downloads
>
> I will write prose for the "too big to fix now" stuff, and I trust the
> other close things will get done by their respective authors. Then we're
> very close to getting a release candidate out.
>
> Congratulations to everyone for a job well done!
>
> Mike
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>

My offer to test on Windows still holds.  The question is test what? 
Assuming that the intent is to support Python 2.6/7 and 3.1/2/3 then 
different versions of Visual Studio are needed as detailed here 
http://bugs.python.org/issue13210.  I can't see much sense in me trying 
to build and test all that lot while other volunteers are doing exactly 
the same thing at the same time.  Is there a cunning plan somewhere to 
cover this that I've missed?

-- 
Cheers.

Mark Lawrence.