[python-committers] Mercurial 3.1 and 2.6 branches are not "inactive"

[Ned Deily]

In article <543ED795.3010403 at jcea.es>, Jesus Cea <jcea at jcea.es> wrote:
> Mercurial branches 3.1 and 2.6 are not "inactive". They are not "merged":
> 
> """
> [jcea at babylon5 cpython]$ hg branches
> default                    93408:fd658692db3a
> 2.7                        93384:7ba47bbfe38d
> 3.1                        90584:c7b93519807a
> 2.6                        90420:23a60d89dbd4
> 3.4                        93406:5fd481150b35 (inactive)
> 3.3                        93403:cda907a02a80 (inactive)
> 3.2                        93299:eac54f7a8018 (inactive)
> """
> 
> I guess they should be "merged" (or "null merged") to 2.7 and to 3.2,
> 3.3, 3.4 and default. I can do it myself, if you think it is appropiate.

Since both 2.6 and 3.1 are now retired, their branches should be marked 
as closed at this point, like earlier retired releases.  Barry?  
Benjamin?

-- 
 Ned Deily,
 nad at acm.org