cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-10315) Add instruction for a permanent git tag for a release
Date Wed, 23 Mar 2016 19:48:25 GMT

    [ https://issues.apache.org/jira/browse/CB-10315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209021#comment-15209021
] 

ASF GitHub Bot commented on CB-10315:
-------------------------------------

GitHub user stevengill opened a pull request:

    https://github.com/apache/cordova-coho/pull/115

    CB-10315 Added apache permanent tag step to tools release process

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/stevengill/cordova-coho patch-52

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-coho/pull/115.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #115
    
----
commit cdea043489c164c4c4f8ffde5f66677c2b2d3366
Author: Steve Gill <stevengill97@gmail.com>
Date:   2016-03-23T19:48:08Z

    CB-10315 Added apache permanent tag step to tools release process

----


> Add instruction for a permanent git tag for a release
> -----------------------------------------------------
>
>                 Key: CB-10315
>                 URL: https://issues.apache.org/jira/browse/CB-10315
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Coho
>            Reporter: Shazron Abdullah
>            Assignee: Steve Gill
>
> After a successful release, we should publish the version tag as a permanent tag as well
per INFRA's instruction below. The tag should be under  "rel/" - so a tag would be for version
1.0 etc "rel/1.0"
> We don't do this for a VOTE just in case there was something wrong with the release.
> From Infra:
> {code}
> Second, we've changed the 'protected' portions of git to primarily
> focus on refs/tags/rel - thus any tags under rel, will have their
> entire commit history. This provides the provenance that the ASF needs
> for releases, while still giving projects the ability to mold their
> repository in the way they see fit.
> Thus when a release vote is successful - part of the release process
> should become tagging the voted upon commit SHA under rel/ to make it
> indelible. ('# git tag rel/v15.4.2 ' or something similar.)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message