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-March/013622.html below:

Patch and Bug Fix Releases

[Python-Dev] PEP 6: Patch and Bug Fix ReleasesGreg Ewing greg@cosc.canterbury.ac.nz
Fri, 16 Mar 2001 12:46:07 +1300 (NZDT)
aahz@pobox.com (Aahz Maruch):

> My preference would be that 2.1.2p is a branch from 2.1.1.

That could be a rather confusing numbering system.

Also, once there has been a patch release, does that mean that
the previous sequence of bugfix-only releases is then closed off?

Even a minor feature addition has the potential to introduce
new bugs. Some people may not want to take even that small
risk, but still want to keep up with bug fixes, so there may
be a demand for a further bugfix release to 2.1.1 after
2.1.2p is released. How would such a release be numbered?

Seems to me that if you're going to have minor feature releases
at all, you need a four-level numbering system: W.X.Y.Z,
where Y is the minor feature release number and Z the bugfix
release number.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
greg@cosc.canterbury.ac.nz	   +--------------------------------------+



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