On Mon, 2019-09-09 at 08:17 -0400, Gary Gregory wrote: > I was just made aware over at Apache Commons that Apache Infra will > protect/preserve tags under "rel/" such that these cannot be deleted > and > should be used for the purpose of tagging releases. Please see below. >
I am for one is very happy that only release tags will be made protected going forward. What we need to do is to rename all existing release tags to conform to the new naming convention ``` X.X.X to rel/vX.X.X ``` Question. Do we also treat RC tags as indelible (immutable)? Oleg > ---------- Forwarded message --------- > From: David Nalley <[email protected]> > Date: Sun, 10 Jan 2016 at 18:00 > Subject: Git status update > To: [email protected] <[email protected]> > > > Greeting PMCs: > (bcc to [email protected]) > > Following direction from the Board, Infrastructure has modified git > to > permit force pushes, and branch/tag deletion. > > In accordance with the guidance that the Board we've implemented a > few > changes you should be aware of: > > First, If a forced commit is pushed, the subsequent commit email will > contain '[Forced Update!]' in the subject line. The hope here is that > it draws extra attention to the situation for a project community to > be aware, and take appropriate action if needed. > > Second, we've changed the 'protected' portions of git to primarily > focus on refs/tags/rel - thus any tags under rel, will have their > entire commit history. This provides the provenance that the ASF > needs > for releases, while still giving projects the ability to mold their > repository in the way they see fit. > > Thus when a release vote is successful - part of the release process > should become tagging the voted upon commit SHA under rel/ to make it > indelible. ('# git tag rel/v15.4.2 ' or something similar.) > > > If you have questions, please feel free to email > [email protected] > > > --David > on behalf of Apache Infrastructure --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
