[python-committers] Cutting Python 2.6
"Martin v. Löwis"
martin at v.loewis.de
Thu Oct 2 07:52:11 CEST 2008
More information about the python-committers mailing list
Thu Oct 2 07:52:11 CEST 2008
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> There should be a way to re-tag only the file(s) that contain the fix. It's possible to edit the tag itself (rather than the trunk/maintenance branch), but then you also need to merge the changes back into the trunk. Also, editing the tag effectively makes it a branch; such usage is discouraged (and it will screw up conversion to, say, bazaar, which assumes a tag denotes a single revision). It would be possible to create a branch just for the release, but that's more tedious. In the specific case, I think it would be best to create the maintenance branch earlier; then only that branch needs to be frozen (instead of the mainline). Regards, Martin
- Previous message: [python-committers] Cutting Python 2.6
- Next message: [python-committers] Cutting Python 2.6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list