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

ASF subversion and git services commented on CB-10315:
------------------------------------------------------

Commit 31ff1c64772b57251500e92ab076640fb707bea7 in cordova-coho's branch 
refs/heads/master from [~stevegill]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=31ff1c6 ]

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

 This closes #115


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to