[
https://issues.apache.org/jira/browse/SLING-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-8337.
------------------------------------
Resolution: Fixed
Fixed with [sling-org-apache-sling-committer-cli commit
d6e58c3|https://github.com/apache/sling-org-apache-sling-committer-cli/commit/d6e58c3]
> Create sub-command to manage the Jira update when staging a release
> -------------------------------------------------------------------
>
> Key: SLING-8337
> URL: https://issues.apache.org/jira/browse/SLING-8337
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Committer CLI 1.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We should add a new command {{release create-jira-new-version}} which takes
> care of the preparatory jira tasks for a new release:
> - creates, if needed, a successor version with the same name and an
> incremented micor version component ( e.g. X.Y.Z+2 )
> - transitions any unresolved issues from the version to be released to the
> successor version
> The incremented version should only be created if no newer version exists,
> e.g. for released version 1.0.0 and already existing version 1.1.0 no 1.0.2
> version should be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
