On Thu, 24 Oct 2019 at 09:28, Emmanuel Bourg <ebo...@apache.org> wrote: > > Le 09/09/2019 à 17:29, Gary Gregory a écrit : > > > What I meant is that, when we successfully create a release, then the > > release tag should go under 'rel/' instead of ''. Sorry for the > > misunderstanding. > > If the vote mail mentions the tag name and the commit hash I don't see > the need to use read-only tags. The mail is archived all around the net > and the commit isn't going away. The risk of losing a release is zero.
That disagrees with the statement made by David Nalley: "thus any tags under rel, will have their entire commit history." Without a fixed tag pointing to a commit, AIUI the commit can be eliminated through a force push. > I can see the downsides of using rel/ tags though: > * it can't be reverted and errors can't be corrected (without bugging > the infra team I guess, but they've more important things to do) That is deliberate, to avoid the lost commit issue. > * it's inconsistent with past releases and we probably don't want to > retag all our repositories > * it doesn't look great, shorter tags look nicer > * it's longer to type when checking out tags from the command line > * it's non standard (never seen that anywhere) It's standard within the ASF now. > * it doesn't solve any actual issue Yes, it does solve an issue - see above. > * we want fewer steps to our release process, not more No, we want as few as possible, but no fewer. > Emmanuel Bourg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
