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/2003-November/040251.html below:

[Python-Dev] Version number in the release-maint23 branch

[Python-Dev] Version number in the release-maint23 branch [Python-Dev] Version number in the release-maint23 branchAnthony Baxter anthony at interlink.com.au
Sat Nov 15 11:46:06 EST 2003
>>> Thomas Heller wrote
> I'd like to change the version number in the CVS release-maint23 branch
> to be able to do correct version checks.
> [ switch from e.g. 2.3.2+ to 2.3.3a0 straight after release of 2.3.2 ]

Should we make this official? In that case, after a major release, should
the version go from, e.g. 2.4b1 -> 2.4b2 -> 2.4c1 -> 2.4 -> 2.4.1a0 ? Or 
should that only happen on the maint branch, and the trunk would go to 
2.5a0?

Consistently-hobgoblinish,
Anthony

-- 
Anthony Baxter     <anthony at interlink.com.au>   
It's never too late to have a happy childhood.


More information about the Python-Dev mailing list

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