Hello. Le mer. 1 avr. 2020 à 13:42, Gary Gregory <garydgreg...@gmail.com> a écrit : > > Option 2 +1 > > The docs should also make sure that release tags are in the form rel/... > which makes them read-only.
Yes, we should certainly update the various howtos. Could you post a link to where this policy is defined? > Do you plan on renaming existing tags? At first sight, that does not seem wise: It will make many vote threads contain dangling references. Gilles > > Gary > > On Wed, Apr 1, 2020, 07:02 Gilles Sadowski <gillese...@gmail.com> wrote: > > > Hello. > > > > This vote is a follow-up of the discussion that started in > > another thread.[1] > > > > As one of the many small steps towards convergence of > > the release processes for all Commons components, it is > > proposed that the same format be used when creating "git" > > tags.[2] > > > > As Gary noted (in the referred thread), the tag is namely used > > when cloning a release candidate.[3] > > > > Alternatives (using the yet-to-be-created tag for the release > > candidate of the first beta version of [Numbers] as an example): > > > > [ ] Option 1: NUMBERS_1_0_BETA1_RC1 > > [ ] Option 2: commons-numbers-1.0-beta1-rc1 > > [ ] Option 3: commons-numbers_v1.0-beta1_rc1 > > > > Please give your choice of the format that should be used from > > now on. > > > > Thanks, > > Gilles > > > > [1] https://markmail.org/message/n457skstbxbirvhp > > [2] https://git-scm.com/book/en/v2/Git-Basics-Tagging > > [3] https://git-scm.com/docs/git-clone --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
