You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2019/04/01 11:03:00 UTC
[jira] [Updated] (SLING-8338) Create sub-command to manage the
Nexus stage repository release when promoting a release
[ https://issues.apache.org/jira/browse/SLING-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu updated SLING-8338:
--------------------------------
Description: We should add a new command {{release nexus-release}} which takes care of releasing the staged artifacts from Nexus for a new release. (was: We should add a new command {{release update-jira}} which takes care of the jira tasks for a new release:
- marks all issues for the released version as 'Closed'
- marks the released version as 'Released'
- creates, if needed, a successor version with the same name and an incremented micor version component ( e.g. X.Y.Z+2 )
- orders the versions so that the successor version is placed right above the released 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.)
> Create sub-command to manage the Nexus stage repository release when promoting a release
> ----------------------------------------------------------------------------------------
>
> Key: SLING-8338
> URL: https://issues.apache.org/jira/browse/SLING-8338
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: CLI 1.0.0
>
>
> We should add a new command {{release nexus-release}} which takes care of releasing the staged artifacts from Nexus for a new release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)