<br><br><div class="gmail_quote">On Thu, Feb 12, 2009 at 10:40, Barry Warsaw <span dir="ltr"><<a href="mailto:barry@python.org">barry@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<div class="Ih2E3d"><br>
<br>
On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou <<a href="mailto:solipsis@pitrou.net" target="_blank">solipsis@pitrou.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jesse Noller <jnoller <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I'm afraid I've gone branch-stupid. I have a a few changes that should<br>
be on the boat for the next release, but I can't for the life of me<br>
remember which branch to push to - right now the changes are on trunk<br>
and py3k.<br>
</blockquote>
<br>
The next release (3.0.1) is tomorrow. Unless those changes are really important,<br>
I humbly advocate deferring them to after tomorrow, for fear that they introduce<br>
last-minute breakage.<br>
<br>
(the branch names are release26-maint and release30-maint, if that's what you're<br>
asking :-))<br>
<br>
</blockquote>
<br>
The changes have been stable since checked in, I have no problems<br>
holding off, but they're also not big. Doc changes, fixes to the<br>
logger and a segfault fix mainly. I have no problem holding off.<br>
</blockquote>
<br></div>
The documentation change is probably safe. Given that I'm tagging 3.0.1 in about 4.5 hours, please be very conservative with any other changes.<br>
</blockquote><div><br>What about the segfault problem? Shouldn't that get in?<br><br>-Brett <br></div></div><br>