[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ee4j-pmc] git tags naming convention?
|
We are using annotated tags. Sometimes it’s good to know who created it and why.
Tag is tied to the release and has the same lifecycle. We create tags as part of our release jobs every time the artifact hits the staging repository. If we need to re-release, we delete the tag and create a new one with the same name. We can do it as many times as needed before the public release. After the public release the tag is frozen.
— Dmitry
> On 31 Oct 2018, at 20:53, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
>
> Ok, so the consensus seems to be to use annotated tags.
>
> Here's a related question...
>
> In an ideal world, a final release of a project will be staged, the
> release review will be successful, and the staged artifacts will be
> released.
>
> But what happens if a problem is discovered after staging and before
> release, or if the release review fails? What if the project *needs*
> to be updated before it is re-staged and released?
>
> In such a scenario, when should the git tag for the release be applied?
> My understanding is that changing the commit that a git tag refers to is
> problematic after the repository has been shared with others.
>
> Is it better to apply and push the git tag for the release when the
> artifacts are staged, and accept the risk that in the unlikely scenario
> the tag may need to be changed?
>
> Or is it better to wait until the release is approved and apply the git
> tag for the release after the fact?
>
> I'm assuming most everyone is doing the former, but I wanted to ask just
> to make sure that's actually considered the "best practice".
>
> Thanks.
>
>
> Bill Shannon wrote on 10/01/2018 03:55 PM:
>> Is there an EE4J-wide convention for how to name the git tags for
>> releases of various sorts?
>> _______________________________________________
>> ee4j-pmc mailing list
>> ee4j-pmc@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
>>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc
