On 07/13/2012 02:00 PM, Jim Meyering wrote: > Reuben Thomas wrote: >> The attached patch simply moves a paragraph so that the step of >> pushing the final (NEWS-updating) commits to git happens before >> uploading any release files. > > Hi Reuben, > > Thanks for the suggestion, but I deliberately chose to > upload the tarball(s) before pushing the tag and commits. > Why? Because the latter step is the only one that is > decisive, and very unlikely to be reverted. If I upload > something I later (in say, the following 10-20 minutes > as I wait for it to appear on the site) want to retract > or replace, I can do that. However, once I push a commit > I feel I cannot reasonably revert that.
Agreed; I also wait to push the NEWS change until after the tarball upload was successful, if only because I have run into situations where I had to straighten out my upload permissions and it took more than a day. Had I pushed the NEWS change in advance, then people would see the NEWS in the git repository but have no matching tarball to download during that window of time where I'm figuring out my upload issues. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
