You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Gary Gregory <ga...@gmail.com> on 2019/09/09 12:18:25 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 Matt Sicker <bo...@gmail.com>.
Right, it'd only be for the approved releases.
On Mon, 9 Sep 2019 at 10:22, Gary Gregory <ga...@gmail.com> wrote:
>
> I think so yes, but RC tags should not be needed there IMO.
>
> Gary
>
> On Mon, Sep 9, 2019, 11:12 Matt Sicker <bo...@gmail.com> wrote:
>
> > So should we copy all the previous release tags into rel/?
> >
> > On Mon, 9 Sep 2019 at 07:18, Gary Gregory <ga...@gmail.com> 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.
> > >
> > > ---------- 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
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
--
Matt Sicker <bo...@gmail.com>
Re: Tagging releases
Posted by Gary Gregory <ga...@gmail.com>.
I think so yes, but RC tags should not be needed there IMO.
Gary
On Mon, Sep 9, 2019, 11:12 Matt Sicker <bo...@gmail.com> wrote:
> So should we copy all the previous release tags into rel/?
>
> On Mon, 9 Sep 2019 at 07:18, Gary Gregory <ga...@gmail.com> 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.
> >
> > ---------- 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
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: Tagging releases
Posted by Matt Sicker <bo...@gmail.com>.
So should we copy all the previous release tags into rel/?
On Mon, 9 Sep 2019 at 07:18, Gary Gregory <ga...@gmail.com> 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.
>
> ---------- 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
--
Matt Sicker <bo...@gmail.com>