incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <>
Subject Re: Git release candidate tagging policy? [was: Re: [VOTE] Apache BatchEE 0.4-incubating]
Date Wed, 28 Sep 2016 15:40:37 GMT
Hi Jochen!

The discussion was about whether a local release build (GIT runs locally and a 'commit' doesn't
push to the canonical ASF repo) should immediately get pushed to the ASF repo or just to a
PMC owned 'other' GIT repo (e.g. on github). 

In various projects we prefer pushing to github because it doesn't pollute the ASF repo in
case the VOTE needs to get cancelled. Remember that you cannot effectively delete a commit/branch/tag
from our repos as they almost immediately get pulled downstream. 

And as the sha1 is cryptographically strong it is guaranteed that when the VOTE succeeds we
get the exact content which was voted upon pushed to the ASF repo anyway.

But otoh if a project decides to use -RC1..17 it's also fine.
BUT: they pollute their branches and tags and they actually would need to do a 2nd VOTE afterwards
on the .Final release. So it is much more work and thus not recommended. But otoh it's not
a blocker neither.


> On Wednesday, 28 September 2016, 16:13, Jochen Wiedmann <>
> > On Mon, Sep 26, 2016 at 10:09 PM, Ate Douma <> wrote:
>>>  Stian, this is established practice in the ASF since the very early 
> days
> Could someone please enlighten me, what "this" is about?
> Thanks,
> Jochen
> -- 
> The next time you hear: "Don't reinvent the wheel!"
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message