Re: [matplotlib-devel] [Matplotlib-users] Plan to merge the matplotlib-py3 branch?

On Wed, Jun 15, 2011 at 9:02 AM, Darren Dale <dsd...@gm...> wrote:

> I suggest we make a 1.1.x branch from the current state of master, and
> consider it as a placeholder for now. Then we bump the version number
> in the py3 repo to *2.0*, merge py3/master back into mpl/master, and
> delete the py3 repo. The reason for bumping to v2.0 is simply to draw
> everyone's attention to the fact the next release will be the first to
> drop support for <=python-2.5. Once folks start working with the
> master (2.0) branch, if we have any complaints that a version 1.1
> release was needed after all, we can cut it from the 1.1.x placeholder
> branch.

This works for me -- I obviously dropped the ball pushing for a 1.1
release, but this will be a good impetus.  Should we give people a
couple of days to close any open tickets they want or push any last
minute changes in that we want before making the 1.1 release branch?
Once we branch, I suggest only release critical bug fixes go in as we
discussed last.