RetroSearch Browse

Thu Dec 30 23:33:20 CET 2010 · https://mail.python.org/pipermail/python-dev/2010-December/107147.html

On 12/30/2010 4:44 PM, Georg Brandl wrote:

>> But you can't use Mercurial's merge functionality for that, right?
>> You have to use some kind of transplant/cherry-picking to merge from the
>> 3.3 branch to the 3.2 branch, right?
>
> Oh, I wrote the above assuming 3.2->3.3 merging.  For the other direction
> you need cherry-picking, yes.

I have the impression that Benjamin plans to continue 3.1 bug 
maintenance for months after 3.2 final rather than issue the last bug 
fix the traditional 1 week after. That would make the sequence 
3.1->3.2->3.3 or 3.1<-3.2<-3.3 or ... . The transition would be a lot 
easier, I think, if 3.1.4 was released along with 3.2, so most of us 
would never have to bother with 3.1 and hg together.

-- 
Terry Jan Reedy

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/107147.html below:

[Python-Dev] Backport troubles with mercurial