[Python-Dev] Non-code changes on "old" branches
Mark Hammond
mhammond at skippinet.com.au
Thu Mar 31 06:31:01 CEST 2011
Hi,
There are a couple of changes I'd like to make and would like some
guidance on policy:
http://bugs.python.org/issue6498 is a documentation bug which exists in
Python 2.6 and later. The patch in that bug touches the docs and a
comment in one source file. Is it acceptable to push that change to the
2.6 branch, or should I start with 2.7?
My request re .hgignore from yesterday didn't get any complaints, so I
intend opening a bug, asking for review here and if I don't get
objections in a day or so, pushing the change. This really should go
all the way back to 2.5 even though that release has long been closed.
Is it acceptable to push a change to .hgignore to the 2.5 branch? If
not, where should I start with such a change?
I ask these questions primarily as the dev guide tells me I should
forward-port all changes - thus, I need to know the earliest versions I
can use before I can even start the process...
Thanks,
Mark
More information about the Python-Dev
mailing list