You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2016/01/25 14:42:51 UTC
Immutable git tags for ASF git repo
All,
Since a month or so we are (again) able to push and delete branches
and tags from ASF git. Infra@ previously shut down the removal options
of branches and tags due to concerns of code provenance and history
rewrites. Those concerns have been alleviated and we now have mostly
full access to the git repository.
For code provenance we need to push immutable tags to git for our
releases under the tags/rel/ references. For example:
git checkout -b build/wicket-7.3.0
perform release steps
git tag rel/wicket-7.3.0
The idea is that the rel/wicket-7.3.0 can't be removed, ever. This
allows for the ASF to track each commit that went into that particular
release. It is not possible to rewrite its history.
So, going forward I'll push all release tags to rel/wicket-x.y.z
I'll also retro-actively push all 7.x release tags to rel/wicket-x.y.z
marking them read only as well. I won't remove the old tags (which is
moot anyway as they are cached locally at many machines already).
>From now on, I won't push bare tags to the ASF repository, but instead
opt to only create tags under rel/wicket-x.y.z
I've also included the release announcement as the tag message for
7.2.0. I'll do this for older releases up to 7.0.0, but not for 6.x or
1.5.x releases.
If we want to do so, perhaps creating a script that parses the release
announcements, attaches them to a signed tag might be in order (as
long as it doesn't push the tags directly to the ASF's repository
prior to review).
Martijn
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: Immutable git tags for ASF git repo
Posted by Martin Funk <ma...@gmail.com>.
+1
2016-01-25 17:29 GMT+01:00 Martin Grigorov <mg...@apache.org>:
> On Mon, Jan 25, 2016 at 5:11 PM, Martijn Dashorst <
> martijn.dashorst@gmail.com> wrote:
>
> > On second thought, what about removing the old tags after they have
> > been copied to rel/wicket-x.y.z?
> >
>
> +1
>
>
> >
> > Would make checking out wicket-x.y branches much simpler.
> >
> > Martijn
> >
> >
> > On Mon, Jan 25, 2016 at 2:42 PM, Martijn Dashorst
> > <ma...@gmail.com> wrote:
> > > All,
> > >
> > > Since a month or so we are (again) able to push and delete branches
> > > and tags from ASF git. Infra@ previously shut down the removal options
> > > of branches and tags due to concerns of code provenance and history
> > > rewrites. Those concerns have been alleviated and we now have mostly
> > > full access to the git repository.
> > >
> > > For code provenance we need to push immutable tags to git for our
> > > releases under the tags/rel/ references. For example:
> > >
> > > git checkout -b build/wicket-7.3.0
> > > perform release steps
> > > git tag rel/wicket-7.3.0
> > >
> > > The idea is that the rel/wicket-7.3.0 can't be removed, ever. This
> > > allows for the ASF to track each commit that went into that particular
> > > release. It is not possible to rewrite its history.
> > >
> > > So, going forward I'll push all release tags to rel/wicket-x.y.z
> > >
> > > I'll also retro-actively push all 7.x release tags to rel/wicket-x.y.z
> > > marking them read only as well. I won't remove the old tags (which is
> > > moot anyway as they are cached locally at many machines already).
> > >
> > > From now on, I won't push bare tags to the ASF repository, but instead
> > > opt to only create tags under rel/wicket-x.y.z
> > >
> > > I've also included the release announcement as the tag message for
> > > 7.2.0. I'll do this for older releases up to 7.0.0, but not for 6.x or
> > > 1.5.x releases.
> > >
> > > If we want to do so, perhaps creating a script that parses the release
> > > announcements, attaches them to a signed tag might be in order (as
> > > long as it doesn't push the tags directly to the ASF's repository
> > > prior to review).
> > >
> > > Martijn
> > >
> > > --
> > > Become a Wicket expert, learn from the best: http://wicketinaction.com
> >
> >
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
> >
>
Re: Immutable git tags for ASF git repo
Posted by Martin Grigorov <mg...@apache.org>.
On Mon, Jan 25, 2016 at 5:11 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:
> On second thought, what about removing the old tags after they have
> been copied to rel/wicket-x.y.z?
>
+1
>
> Would make checking out wicket-x.y branches much simpler.
>
> Martijn
>
>
> On Mon, Jan 25, 2016 at 2:42 PM, Martijn Dashorst
> <ma...@gmail.com> wrote:
> > All,
> >
> > Since a month or so we are (again) able to push and delete branches
> > and tags from ASF git. Infra@ previously shut down the removal options
> > of branches and tags due to concerns of code provenance and history
> > rewrites. Those concerns have been alleviated and we now have mostly
> > full access to the git repository.
> >
> > For code provenance we need to push immutable tags to git for our
> > releases under the tags/rel/ references. For example:
> >
> > git checkout -b build/wicket-7.3.0
> > perform release steps
> > git tag rel/wicket-7.3.0
> >
> > The idea is that the rel/wicket-7.3.0 can't be removed, ever. This
> > allows for the ASF to track each commit that went into that particular
> > release. It is not possible to rewrite its history.
> >
> > So, going forward I'll push all release tags to rel/wicket-x.y.z
> >
> > I'll also retro-actively push all 7.x release tags to rel/wicket-x.y.z
> > marking them read only as well. I won't remove the old tags (which is
> > moot anyway as they are cached locally at many machines already).
> >
> > From now on, I won't push bare tags to the ASF repository, but instead
> > opt to only create tags under rel/wicket-x.y.z
> >
> > I've also included the release announcement as the tag message for
> > 7.2.0. I'll do this for older releases up to 7.0.0, but not for 6.x or
> > 1.5.x releases.
> >
> > If we want to do so, perhaps creating a script that parses the release
> > announcements, attaches them to a signed tag might be in order (as
> > long as it doesn't push the tags directly to the ASF's repository
> > prior to review).
> >
> > Martijn
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
Re: Immutable git tags for ASF git repo
Posted by Martijn Dashorst <ma...@gmail.com>.
On second thought, what about removing the old tags after they have
been copied to rel/wicket-x.y.z?
Would make checking out wicket-x.y branches much simpler.
Martijn
On Mon, Jan 25, 2016 at 2:42 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> All,
>
> Since a month or so we are (again) able to push and delete branches
> and tags from ASF git. Infra@ previously shut down the removal options
> of branches and tags due to concerns of code provenance and history
> rewrites. Those concerns have been alleviated and we now have mostly
> full access to the git repository.
>
> For code provenance we need to push immutable tags to git for our
> releases under the tags/rel/ references. For example:
>
> git checkout -b build/wicket-7.3.0
> perform release steps
> git tag rel/wicket-7.3.0
>
> The idea is that the rel/wicket-7.3.0 can't be removed, ever. This
> allows for the ASF to track each commit that went into that particular
> release. It is not possible to rewrite its history.
>
> So, going forward I'll push all release tags to rel/wicket-x.y.z
>
> I'll also retro-actively push all 7.x release tags to rel/wicket-x.y.z
> marking them read only as well. I won't remove the old tags (which is
> moot anyway as they are cached locally at many machines already).
>
> From now on, I won't push bare tags to the ASF repository, but instead
> opt to only create tags under rel/wicket-x.y.z
>
> I've also included the release announcement as the tag message for
> 7.2.0. I'll do this for older releases up to 7.0.0, but not for 6.x or
> 1.5.x releases.
>
> If we want to do so, perhaps creating a script that parses the release
> announcements, attaches them to a signed tag might be in order (as
> long as it doesn't push the tags directly to the ASF's repository
> prior to review).
>
> Martijn
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
--
Become a Wicket expert, learn from the best: http://wicketinaction.com