RetroSearch Browse

Mon Nov 8 18:28:32 CET 2004 · https://mail.python.org/pipermail/python-dev/2004-November/049841.html

[Aahz]
#- As soon as the new version is released, if there is no bugfix planned
#- for that issue.  Two versions later (i.e. 2.3 in this case) 
#- even if it
#- looks like it ought to be fixed in 2.1 -- we haven't been 
#- doing bugfixes
#- more than one version old.

[Martin v. Löwis]
#- It is (IMO) fine to close anything now that is fixed in 2.3 
#- and newer.
#- The proper "Resolution" is "Fixed", with a Comment "Fixed in 2.3".

[Anthony Baxter]
#- As for the original query, about what to do with bugs filed against
#- 2.1.x - I'd suggest closing them. There's a vanishingly small chance
#- that there will ever be another 2.1 or 2.2 release.

A bug count from SF:

Group  Quantity
2.1.1      2
2.1.2      3
2.2       20
2.2.1     17
2.2.1c     1
2.2.2     35
2.2.3     24
        -----
         102

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.

So I propose to take the job of getting into each one of these bugs and
comment:

"""
Please, could you verify if this problem persists in Python 2.3.4 or 2.4?

If yes, in which version? Can you provide a test case?

If the problem is solved, from which version?

Note that if you fail to answer in one month, I'll close this bug as "Won't
fix".

Thank you!
"""

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.

What do you think of this? If you're ok, I'll do it.

[Trent Mick]
#- Maybe a "Known Issues in Python 2.1" PEP which refers to these bug 
#- numbers and then close the bugs? I don't want to make more work for 
#- people, though.

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.

A PEP with this kind of uncertainty worths it?

Thanks for everything.

.	Facundo

#- -----Mensaje original-----
#- De: Trent Mick [mailto:trentm at ActiveState.com]
#- Enviado el: Viernes, 05 de Noviembre de 2004 15:26
#- Para: Anthony Baxter
#- CC: Aahz; Batista, Facundo; Python Dev (E-mail)
#- Asunto: Re: [Python-Dev] Policy about old Python versions
#- 
#- 
#- Anthony Baxter wrote:
#- > As for the original query, about what to do with bugs filed against
#- > 2.1.x - I'd suggest closing them. There's a vanishingly 
#- small chance
#- > that there will ever be another 2.1 or 2.2 release.
#- 
#- Maybe a "Known Issues in Python 2.1" PEP which refers to these bug 
#- numbers and then close the bugs? I don't want to make more work for 
#- people, though.
#- 
#- Trent
#- 
#- -- 
#- Trent Mick
#- trentm at activestate.com
#- 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20041108/32052fcc/attachment-0001.html

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-November/049841.html below:

[Python-Dev] Policy about old Python versions