A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-December/018816.html below:

[Python-Dev] Release criteria

[Python-Dev] Release criteriaMartin von Loewis loewis@informatik.hu-berlin.de
Sun, 2 Dec 2001 14:53:33 +0100 (MET)
Now that there are only ten days left for the release candidate, I
wonder whether there are any release criteria beyond "builds on
Windows".

In particular, I think that the release candidate should not be
produced until "critical" SF bugs have been resolved. In #420851,
Barry indicates that bugs with a priority higher than six will block a
release. This sounds reasonable.

Looking at the remaining bugs, we see

Priority 8: two reports (assigned to loewis and nobody)

Priority 7: 11 reports (6x akuchling, 3x gvanrossum, 
                        1x jackjansen, 1x fdrake)

Given that the oldest of these reports is from 2001-07-30, I think it
is unlikely that they will be all resolved within ten days. That seems
to suggest one of the following alternatives:

1. Move the deadline for the release candidate,
2. Lower the priority for some of the reports,
3. Move the threshold for release-critical bugs (to, say, 8),
4. Give up the notion of release-critical bugs (which I would regret,
   since I hope "my" prio-8-bug should be fixed; it'll just take
   some more days).

Regards,
Martin




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