You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Gary Gregory <ga...@gmail.com> on 2019/09/09 12:17:10 UTC
Tagging releases
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.
---------- Forwarded message ---------
From: David Nalley <ke...@apache.org>
Date: Sun, 10 Jan 2016 at 18:00
Subject: Git status update
To: infrastructure@apache.org <in...@apache.org>
Greeting PMCs:
(bcc to pmcs@apache.org)
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 infrastructure@apache.org
--David
on behalf of Apache Infrastructure
Re: Tagging releases
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Mon, 2019-09-09 at 10:24 -0400, Gary Gregory wrote:
> On Mon, Sep 9, 2019 at 9:33 AM Oleg Kalnichevski <ol...@apache.org>
> wrote:
>
> > 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)?
> >
>
> My view is no but asking on @infra or @legal seems like a good idea.
>
I agree. I guess as long as we all are on the same page we do not need
to bother the infra.
Oleg
> Gary
>
>
> > Oleg
> >
> > > ---------- Forwarded message ---------
> > > From: David Nalley <ke...@apache.org>
> > > Date: Sun, 10 Jan 2016 at 18:00
> > > Subject: Git status update
> > > To: infrastructure@apache.org <in...@apache.org>
> > >
> > >
> > > Greeting PMCs:
> > > (bcc to pmcs@apache.org)
> > >
> > > 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
> > > infrastructure@apache.org
> > >
> > >
> > > --David
> > > on behalf of Apache Infrastructure
> >
> >
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> > For additional commands, e-mail: dev-help@hc.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Tagging releases
Posted by Gary Gregory <ga...@gmail.com>.
On Mon, Sep 9, 2019 at 9:33 AM Oleg Kalnichevski <ol...@apache.org> wrote:
> 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)?
>
My view is no but asking on @infra or @legal seems like a good idea.
Gary
> Oleg
>
> > ---------- Forwarded message ---------
> > From: David Nalley <ke...@apache.org>
> > Date: Sun, 10 Jan 2016 at 18:00
> > Subject: Git status update
> > To: infrastructure@apache.org <in...@apache.org>
> >
> >
> > Greeting PMCs:
> > (bcc to pmcs@apache.org)
> >
> > 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
> > infrastructure@apache.org
> >
> >
> > --David
> > on behalf of Apache Infrastructure
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Re: Tagging releases
Posted by Gary Gregory <ga...@gmail.com>.
On Fri, Sep 27, 2019 at 10:08 AM Oleg Kalnichevski <ol...@apache.org> wrote:
> On Mon, 2019-09-09 at 15:33 +0200, Oleg Kalnichevski wrote:
> > 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 would like to try an rename the existing release tags this weekend.
>
+1
Gary
>
> Oleg
>
>
> >
> > 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 <ke...@apache.org>
> > > Date: Sun, 10 Jan 2016 at 18:00
> > > Subject: Git status update
> > > To: infrastructure@apache.org <in...@apache.org>
> > >
> > >
> > > Greeting PMCs:
> > > (bcc to pmcs@apache.org)
> > >
> > > 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
> > > infrastructure@apache.org
> > >
> > >
> > > --David
> > > on behalf of Apache Infrastructure
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> > For additional commands, e-mail: dev-help@hc.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
>
Re: Tagging releases
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Mon, 2019-09-09 at 15:33 +0200, Oleg Kalnichevski wrote:
> 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 would like to try an rename the existing release tags this weekend.
Oleg
>
> 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 <ke...@apache.org>
> > Date: Sun, 10 Jan 2016 at 18:00
> > Subject: Git status update
> > To: infrastructure@apache.org <in...@apache.org>
> >
> >
> > Greeting PMCs:
> > (bcc to pmcs@apache.org)
> >
> > 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
> > infrastructure@apache.org
> >
> >
> > --David
> > on behalf of Apache Infrastructure
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Tagging releases
Posted by Oleg Kalnichevski <ol...@apache.org>.
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 <ke...@apache.org>
> Date: Sun, 10 Jan 2016 at 18:00
> Subject: Git status update
> To: infrastructure@apache.org <in...@apache.org>
>
>
> Greeting PMCs:
> (bcc to pmcs@apache.org)
>
> 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
> infrastructure@apache.org
>
>
> --David
> on behalf of Apache Infrastructure
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org