Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-18685

Rules for naming git (release) tags?

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Fix Version/s: None
    • Component/s: Git
    • Labels:
      None
    • Project:
      Cordova

      Description

      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)

        Attachments

          Activity

            People

            • Assignee:
              humbedooh Daniel Gruno
              Reporter:
              Sujan12 Jan Piotrowski (janpio)
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: