On Sun, 30 Oct 2022 at 18:48, Gary D. Gregory <[email protected]> wrote: > > There better never be RC tags under the rel/ prefix, that space is only for > releases and lives forever. > > Gary
What I think has happened is that Matt created the tag during an early cut of the beta RC1 release. I pulled the tag during development, and the tag was then deleted by Matt from the master repo when he rerolled the beta1 RC1 (with a different tag name). So I had a copy of it locally which I then pushed back to the repo when I made the recent release for 1.1. The tags are now: > git tag -l NUMBERS_1_0_B1_RC1 commons-numbers-1.0-beta1-rc1 commons-numbers-1.0-rc1 commons-numbers-1.1-RC1 rel/commons-numbers-1.0 rel/commons-numbers-1.0-beta1 The two rc1 tags (1.0-beta1 and 1.0) match the official tags under the rel directory. The NUMBERS_1_0_B1_RC1 is an error as it does not point to an official release commit. I will delete this tag. If it has been pulled by another committer it may be pushed back again in the future; hopefully we can minimise this occurring by updating the release notes on how to push a specific tag and not using 'git push --tags'. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
