There should be a way to re-tag only the file(s) that contain the fix.
On Wed, Oct 1, 2008 at 4:00 PM, Anthony Baxter email@example.com wrote:
If there's a screwup, and you need to recut the branch, you want to be sure someone else hasn't been helpful and added something else to the repo.
On Thu, Oct 2, 2008 at 9:37 AM, Jesus Cea firstname.lastname@example.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Barry Warsaw wrote:
IIUC, the critical bottleneck is tagging the tree, so the RM needs to make it far enough through the PEP to get to that point. Of course that does mean freezing the tree, and I don't think it's too difficult to do that.
I always found strange the need to freeze the tree. When a svn tag is created, the build process should use that tag to extract the files and build the release, while the repository is being updated normally.
In fact in a *.0 release, the tag should be a branch actually.
Sure I'm missing something...
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ email@example.com - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:firstname.lastname@example.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBSOP7oJlgi5GaxT1NAQKmwQP/XTepaw9fFqf4b3VWsocvj0s4sb7THKgF cVi7Rf424YD+i7AJzMe0aFMEsrhvor1Ma/KMMXdypymxXkUapuJmLIP6R3BWZzyp sCDzRifhgHJg6LCq3TpIPvYseurUR1P0hgLZEKf5K/EAO+BJc6RIknBOgNS0RuHG SNs5cVMhe7g= =VRp9 -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list email@example.com http://mail.python.org/mailman/listinfo/python-committers
python-committers mailing list firstname.lastname@example.org http://mail.python.org/mailman/listinfo/python-committers