-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/26/2010 07:40 AM, "Martin v. Löwis" wrote:
>> For example, it might be interesting to bring old release
>> tags in line with newer tags (so Release_1_0 would become r10), or
>> maybe use clean tags similar to what we do with hg itself (r266 would
>> become just 2.6.6), or just remove some tags. Is this a good idea at
>> all, or should we just leave everything the way it is now?
>
> Removing tags sounds fine with me. Renaming them not so; I fail to see
> the point.
One point is to remove inconsistencies tied to CVS-era restrictions:
the tags which correspond to (define) actual numbered releases have
goofy names due to CVSism ('r266' is a ridiculously hard-to-figure-out
alternative to '2.6.6').
Given that nobody will be able to update checkouts in place anyway, I
think taking this opportunity to use "real" version IDs for tags would
be a much better than sticking with the old cruft.
Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyfXj4ACgkQ+gerLs4ltQ6fZQCeJIQzz4CO9D/Jc1ryeO9zhiUA
/EcAn3IkPDOpJetd9kC6/gqpNqN8JHkC
=0roB
-----END PGP SIGNATURE-----
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
