Re: faulty releases and pypi access [update]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephan Richter wrote:
> On Wednesday 26 September 2007 05:02, Christian Theune wrote:
>> Hmm. While doing that I also noticed that we were at 3.4.0a1 yesterday
>> evening. The stable release was made from that without making a
>> maintenance branch and bumping the trunk to 3.5.
> 
> There is conflicting information here. :-) Some people say we need branches, 
> others say we don't. And where is an agreed-upon document that you have to 
> list the next version in the setup.py file after the release? Because I 
> disagree with that, since you cannot know the next version.

+1,  The trunk should *always* say 'unreleased' or 'trunk', except in
the five minutes before cutting a release tag (if not using a release
branch).  Release branches should have '-branch' or something appended
to the version, except just before cutting a release tag.

Anything else makes it too easy to cut a premature / broken release;
such mistakes are going to damange  our story if we don't get out ahead
of them.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          [email protected]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG+nGq+gerLs4ltQ4RAtrkAJoDIeCeHW3BVdlWYLklwf6MrOV2MwCgy43W
enYWkDaVC0IHZV4Fb0K7KDA=
=WGvo
-----END PGP SIGNATURE-----