[python-committers] Closing the 2.6 branch?

["Martin v. Löwis"]

Am 30.10.13 15:13, schrieb Barry Warsaw:
> Now that 2.6.9 is out, I wonder if there's anything we can or
> should do to the Mercurial repository to explicitly prevent commits
> to the 2.6 branch?  We have we done to older branches?

I think closing the branch is just right; it's done through "hg commit
--close-branch".

> We have we done to older branches?

hg branches -c will tell:

default                    86195:63a1ee94b3ed
2.7                        86192:0820e8394d96
3.3                        86193:249ba942a6d4 (inaktiv)
2.6                        85914:6d7ae764b4f2 (inaktiv)
3.2                        85752:ef90c40fe6cf (inaktiv)
3.1                        85751:713d71048ab9 (inaktiv)
2.5                        73244:b48e1b48e670 (geschlossen)
3.0                        68249:4cd9f5e89061 (geschlossen)
legacy-trunk               68241:b77918288f7d (geschlossen)
2.4                        68239:ceec209b26d4 (geschlossen)
2.3                        68237:364638d6434d (geschlossen)
2.2                        68235:61b0263d6881 (geschlossen)
2.1                        68233:e849d484029f (geschlossen)
2.0                        68231:5fd74354d73b (geschlossen)

In addition, I *think* we have a hook on the master that prevents
further pushes to the branch.

> Also, can anybody think of anything in the devguide that needs to
> be updated?

Not the devguide. If anywhere, in PEP 101.

Regards,
Martin