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 binariesmatplotlib - 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: