<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RE: [Python-Dev] Policy about old Python versions</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>[Aahz]</FONT>
<BR><FONT SIZE=2>#- As soon as the new version is released, if there is no bugfix planned</FONT>
<BR><FONT SIZE=2>#- for that issue. Two versions later (i.e. 2.3 in this case) </FONT>
<BR><FONT SIZE=2>#- even if it</FONT>
<BR><FONT SIZE=2>#- looks like it ought to be fixed in 2.1 -- we haven't been </FONT>
<BR><FONT SIZE=2>#- doing bugfixes</FONT>
<BR><FONT SIZE=2>#- more than one version old.</FONT>
</P>
<P><FONT SIZE=2>[Martin v. Löwis]</FONT>
<BR><FONT SIZE=2>#- It is (IMO) fine to close anything now that is fixed in 2.3 </FONT>
<BR><FONT SIZE=2>#- and newer.</FONT>
<BR><FONT SIZE=2>#- The proper "Resolution" is "Fixed", with a Comment "Fixed in 2.3".</FONT>
</P>
<P><FONT SIZE=2>[Anthony Baxter]</FONT>
<BR><FONT SIZE=2>#- As for the original query, about what to do with bugs filed against</FONT>
<BR><FONT SIZE=2>#- 2.1.x - I'd suggest closing them. There's a vanishingly small chance</FONT>
<BR><FONT SIZE=2>#- that there will ever be another 2.1 or 2.2 release.</FONT>
</P>
<P><FONT SIZE=2>A bug count from SF:</FONT>
</P>
<P><FONT SIZE=2>Group Quantity</FONT>
<BR><FONT SIZE=2>2.1.1 2</FONT>
<BR><FONT SIZE=2>2.1.2 3</FONT>
<BR><FONT SIZE=2>2.2 20</FONT>
<BR><FONT SIZE=2>2.2.1 17</FONT>
<BR><FONT SIZE=2>2.2.1c 1</FONT>
<BR><FONT SIZE=2>2.2.2 35</FONT>
<BR><FONT SIZE=2>2.2.3 24</FONT>
<BR><FONT SIZE=2> -----</FONT>
<BR><FONT SIZE=2> 102</FONT>
</P>
<P><FONT SIZE=2>Of 769 open bugs, that represents more than a 13%: I think that closing them or reassigning them to a newer version (if the problem continues) will make work with bugs a little easier.</FONT></P>
<P><FONT SIZE=2>So I propose to take the job of getting into each one of these bugs and comment:</FONT>
</P>
<P><FONT SIZE=2>"""</FONT>
<BR><FONT SIZE=2>Please, could you verify if this problem persists in Python 2.3.4 or 2.4?</FONT>
</P>
<P><FONT SIZE=2>If yes, in which version? Can you provide a test case?</FONT>
</P>
<P><FONT SIZE=2>If the problem is solved, from which version?</FONT>
</P>
<P><FONT SIZE=2>Note that if you fail to answer in one month, I'll close this bug as "Won't fix".</FONT>
</P>
<P><FONT SIZE=2>Thank you!</FONT>
<BR><FONT SIZE=2>"""</FONT>
</P>
<P><FONT SIZE=2>If nobody answers in a month, close the bug. The worst problem that we can have here is to close a bug that still exists.</FONT></P>
<P><FONT SIZE=2>What do you think of this? If you're ok, I'll do it.</FONT>
</P>
<BR>
<P><FONT SIZE=2>[Trent Mick]</FONT>
<BR><FONT SIZE=2>#- Maybe a "Known Issues in Python 2.1" PEP which refers to these bug </FONT>
<BR><FONT SIZE=2>#- numbers and then close the bugs? I don't want to make more work for </FONT>
<BR><FONT SIZE=2>#- people, though.</FONT>
</P>
<P><FONT SIZE=2>This idea of compilate all the problems of those past versions in a PEP is good, but I can not do it: in the best case I can compile all the "once opened bugs" for those versions, but not verify that each is really a problem.</FONT></P>
<P><FONT SIZE=2>A PEP with this kind of uncertainty worths it?</FONT>
</P>
<BR>
<P><FONT SIZE=2>Thanks for everything.</FONT>
</P>
<P><FONT SIZE=2>. Facundo</FONT>
</P>
<BR>
<P><FONT SIZE=2>#- -----Mensaje original-----</FONT>
<BR><FONT SIZE=2>#- De: Trent Mick [<A HREF="mailto:trentm@ActiveState.com">mailto:trentm@ActiveState.com</A>]</FONT>
<BR><FONT SIZE=2>#- Enviado el: Viernes, 05 de Noviembre de 2004 15:26</FONT>
<BR><FONT SIZE=2>#- Para: Anthony Baxter</FONT>
<BR><FONT SIZE=2>#- CC: Aahz; Batista, Facundo; Python Dev (E-mail)</FONT>
<BR><FONT SIZE=2>#- Asunto: Re: [Python-Dev] Policy about old Python versions</FONT>
<BR><FONT SIZE=2>#- </FONT>
<BR><FONT SIZE=2>#- </FONT>
<BR><FONT SIZE=2>#- Anthony Baxter wrote:</FONT>
<BR><FONT SIZE=2>#- > As for the original query, about what to do with bugs filed against</FONT>
<BR><FONT SIZE=2>#- > 2.1.x - I'd suggest closing them. There's a vanishingly </FONT>
<BR><FONT SIZE=2>#- small chance</FONT>
<BR><FONT SIZE=2>#- > that there will ever be another 2.1 or 2.2 release.</FONT>
<BR><FONT SIZE=2>#- </FONT>
<BR><FONT SIZE=2>#- Maybe a "Known Issues in Python 2.1" PEP which refers to these bug </FONT>
<BR><FONT SIZE=2>#- numbers and then close the bugs? I don't want to make more work for </FONT>
<BR><FONT SIZE=2>#- people, though.</FONT>
<BR><FONT SIZE=2>#- </FONT>
<BR><FONT SIZE=2>#- Trent</FONT>
<BR><FONT SIZE=2>#- </FONT>
<BR><FONT SIZE=2>#- -- </FONT>
<BR><FONT SIZE=2>#- Trent Mick</FONT>
<BR><FONT SIZE=2>#- trentm@activestate.com</FONT>
<BR><FONT SIZE=2>#- </FONT>
</P>
</BODY>
</HTML>