On Mon, Jun 13, 2011 at 2:29 PM, Michael Droettboom <md...@stsci.edu> wrote:
> On 06/13/2011 01:38 PM, Darren Dale wrote:
>>
>> On Mon, Jun 13, 2011 at 12:25 PM, Michael Droettboom<md...@stsci.edu>
>>  wrote:
>>>
>>> This was recently discussed in the thread "v1.0.x branch seems confused."
>>>
>>> I (believe) the consensus was to get out another v1.0.x maintenance
>>> release out in the near future (which would not support py3k, but would
>>> still support Python 2.4), and then merge the py3 branch into master so
>>> it starts to get some more testing before making the next major release.
>>>
>>> I'm just today merging master into py3 so that when we are ready to do
>>> the merge the other way most of the hard work will have already been
>>> done.
>>
>> Are there features already in master that should be supported by
>> <python-2.6? If so, I think we should consider releasing 1.1.0 and
>> making a 1.1.x maintenance branch before merging the py3 stuff back
>> into master. Then mpl-1.2 could be the first to support py3.
>
> That's a good question.  We're now *officially* on 2.7 in my environment, so
> I don't have any compulsion to raise my hand here.  But others may.  Speak
> up!  :)

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.

Darren

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to