[jira] [Commented] (PROTON-790) Use git tag for release (rather than branch)
[ https://issues.apache.org/jira/browse/PROTON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257836#comment-14257836 ] Rafael H. Schloming commented on PROTON-790: I'll update the release script to use tags for the next alpha. > Use git tag for release (rather than branch) > > > Key: PROTON-790 > URL: https://issues.apache.org/jira/browse/PROTON-790 > Project: Qpid Proton > Issue Type: Improvement > Components: release >Affects Versions: 0.9 >Reporter: Andrew Stitcher >Assignee: Rafael H. Schloming >Priority: Minor > > I think it would make sense to use git tags to indicate the versions of > releases including alphas and betas. > So instead of having branch with a single change on it we should use a tag > to indicate a release. This would also allow the branching structure and the > releases to be independent. > As an example the recent 0.9-alpha-1 could be a tag on a 0.9-release branch. > Or it could just be a tag on a one change branch (to change the version). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-790) Use git tag for release (rather than branch)
[ https://issues.apache.org/jira/browse/PROTON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257582#comment-14257582 ] Andrew Stitcher commented on PROTON-790: Another benefit of using tags is that they can be signed by the release manager. > Use git tag for release (rather than branch) > > > Key: PROTON-790 > URL: https://issues.apache.org/jira/browse/PROTON-790 > Project: Qpid Proton > Issue Type: Improvement > Components: release >Affects Versions: 0.9 >Reporter: Andrew Stitcher >Assignee: Rafael H. Schloming >Priority: Minor > > I think it would make sense to use git tags to indicate the versions of > releases including alphas and betas. > So instead of having branch with a single change on it we should use a tag > to indicate a release. This would also allow the branching structure and the > releases to be independent. > As an example the recent 0.9-alpha-1 could be a tag on a 0.9-release branch. > Or it could just be a tag on a one change branch (to change the version). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-790) Use git tag for release (rather than branch)
[
https://issues.apache.org/jira/browse/PROTON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257581#comment-14257581
]
Andrew Stitcher commented on PROTON-790:
In the current tree
{code}git tag 0.9-alpha-1 origin/0.9-alpha-1{code}
will create the kind of tag I'm talking about. It will need to be pushed after
creating in the local repository too.
{code}git push origin 0.9-alpha-1{code}
> Use git tag for release (rather than branch)
>
>
> Key: PROTON-790
> URL: https://issues.apache.org/jira/browse/PROTON-790
> Project: Qpid Proton
> Issue Type: Improvement
> Components: release
>Affects Versions: 0.9
>Reporter: Andrew Stitcher
>Assignee: Rafael H. Schloming
>Priority: Minor
>
> I think it would make sense to use git tags to indicate the versions of
> releases including alphas and betas.
> So instead of having branch with a single change on it we should use a tag
> to indicate a release. This would also allow the branching structure and the
> releases to be independent.
> As an example the recent 0.9-alpha-1 could be a tag on a 0.9-release branch.
> Or it could just be a tag on a one change branch (to change the version).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
