> - In the checkin message, indicate which file version from the
> mainline is being copied into the release branch.
Sounds good.
> - In Misc/NEWS, indicate what bugs have been fixed by installing these
> patches. If it was a patch in response to a SF bug report, listing
> the SF bug id should be sufficient; I've put some instructions into
> Misc/NEWS on how to retrieve the bug report for a bug id.
Good, too.
> I've done so only for the _tkinter patch, which was both listed as
> critical, and which closed 2 SF bug reports. I've verified that the
> sre_parse patch also closes a number of SF bug reports, but have not
> copied it to the release branch.
I'm a little concerned that the 2.0 branch is being updated without a
2.0.1 target created, but it's quite possible my understanding of how
this should work is faulty.
--
--- Aahz <*> (Copyright 2001 by aahz@pobox.com)
Androgynous poly kinky vanilla queer het Pythonista http://www.rahul.net/aahz/
Hugs and backrubs -- I break Rule 6
Three sins: BJ, B&J, B&J
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4