Mercurial 3.1 and 2.6 branches are not "inactive"
Mercurial branches 3.1 and 2.6 are not "inactive". They are not "merged":
""" [jcea@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.
-- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
In article <543ED795.3010403@jcea.es>, Jesus Cea <jcea@jcea.es> wrote:
Mercurial branches 3.1 and 2.6 are not "inactive". They are not "merged":
""" [jcea@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@acm.org
On Oct 15, 2014, at 01:47 PM, Ned Deily wrote:
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?
2.6 for sure. I don't know what actually has to happen to mark them closed, but there will not be another 2.6 release.
Cheers, -Barry
On 15/10/14 22:58, Barry Warsaw wrote:
On Oct 15, 2014, at 01:47 PM, Ned Deily wrote:
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?2.6 for sure. I don't know what actually has to happen to mark them closed, but there will not be another 2.6 release.
Looks like touching 2.6 is forbidden:
""" jcea@ubuntu:cpython$ hg up -r 2.6 jcea@ubuntu:cpython$ hg commit --close-branch -m "2.6 is no longer maintained" jcea@ubuntu:cpython$ hg push pushing to ssh://hg@hg.python.org/cpython/ searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 0 changes to 0 files (-1 heads) remote: - changeset 25b79170c319 on disallowed branch '2.6'! remote: * Please strip the offending changeset(s) remote: * and re-do them, if needed, on another branch! remote: transaction abort! remote: rollback completed remote: abort: pretxnchangegroup.checkbranch hook failed """
If configuring mercurial HOOKS to disallow branches is documented somewhere in the release manager guide, it should do the step of closing the branch first :-).
-- Jesús Cea Avión _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
In article <20141015165846.2b7a70f1@limelight.wooz.org>, Barry Warsaw <barry@python.org> wrote:
2.6 for sure. I don't know what actually has to happen to mark them closed, but there will not be another 2.6 release.
Benjamin has taken care of closing both the 2.6 and 3.1 branches. RIP
-- Ned Deily, nad@acm.org
participants (3)
-
Barry Warsaw -
Jesus Cea -
Ned Deily