matplotlib v1.1.1 (bugfix) rc1 on Thursday

In article
<CAGD8yY_bisEWrbM2pzo8PeWaXeU0fLv1araurSwg_juwSSLh3g@...150...>,

> I think we are pretty close to cleaning up issues and PRs related to
> v1.1.x, so I'd like to cut the release candidate this Thursday. Let's
> continue to hammer on closing open issues and pull requests, and flag
> anything that needs to be addressed before the release as
> "release_critical" in the issue tracker. If there are show stoppers I am
> not aware of, chime in.
>
>
The tarballs for the v1.1.1 release candidate 1 (rc1) are uploaded to and
are available for testing and building binaries

matplotlib - Browse /matplotlib/matplotlib-1.1.1 at SourceForge.net

I have uploaded the Mac builds (no Python 2.6 yet; do we really need
that?). They pass all unit tests and the 32-bit version seems to work
well with my software.

The included pytz is outdated (and I did not bother to uprev it in the
binaries I uploaded); would somebody be willing to update that before we
cut the final releases, or is that considered too risky at this late
date?

-- Russell

···

John Hunter <jdh2358@...149...> wrote:

On Mon, Mar 19, 2012 at 12:58 PM, John Hunter > <jdh2358@...149...> wrote:

It feels too risky to me post-rc. How critical do you think the updates are? We are planning on moving our attention to a master release 1.2.x as soon as this is out, and we can update ahead of that. And for people who need the latest, they can always install their own.

JDH

···

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen <rowen@…272…748…> wrote:

The included pytz is outdated (and I did not bother to uprev it in the

binaries I uploaded); would somebody be willing to update that before we

cut the final releases, or is that considered too risky at this late

date?

Might be nice to upload some python2.6 builds for the actual release, but I don’t see this as necessary for the testers since there are no important differences between 2.6 and 2.7 as far as v1.1.x is concerned.

JDH

···

On Fri, Mar 23, 2012 at 12:55 PM, Russell E. Owen <rowen@…272…748…> wrote:

I have uploaded the Mac builds (no Python 2.6 yet; do we really need

that?). They pass all unit tests and the 32-bit version seems to work

well with my software.