infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Piotrowski (janpio) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-18685) Rules for naming git (release) tags?
Date Tue, 02 Jul 2019 13:35:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-18685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jan Piotrowski (janpio) updated INFRA-18685:
--------------------------------------------
    Status: Waiting for Infra  (was: Waiting for user)

> Rules for naming git (release) tags?
> ------------------------------------
>
>                 Key: INFRA-18685
>                 URL: https://issues.apache.org/jira/browse/INFRA-18685
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git
>            Reporter: Jan Piotrowski (janpio)
>            Assignee: Daniel Gruno
>            Priority: Minor
>
> Apache Cordova currently uses `x.y.z` to tag a release to be voted on, and `rel/x.y.z`
to tag the same commit after a vote succeeded and the archive is published (this second tag
is called the "permanent Apache release tag" in our documentation). 
> As this is causing confusion to our users (they see the initial tag an expect it to be
published already, but can't find it as we have to wait for the finished vote - which might
fail) etc. I was thinking about changing this. 
> During the discussions about this, several people mentioned that this was "required by
Apache process" and "an INFRA thing" (paraphrased). My initial googling for documentation
on this didn't turn anything up.
> Can you help me understand if there is indeed such a requirement to name the tags this
specific way? (both from a technical and process view) Or would you and Apache be fine with
whatever we choose, as long as the after vote tag is permanent and does not get changed after
the fact?
> (Background: Apache Cordova is using GitHub for git, our tools and release process could
handle whatever we define)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message