You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mnemonic.apache.org by "Wang, Gang (Jira)" <ji...@apache.org> on 2021/01/02 22:08:00 UTC

[jira] [Resolved] (MNEMONIC-584) Separate release candidate build from releasing and bump version

     [ https://issues.apache.org/jira/browse/MNEMONIC-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wang, Gang resolved MNEMONIC-584.
---------------------------------
    Fix Version/s: 0.13.0
       Resolution: Fixed

Resolved.

> Separate release candidate build from releasing and bump version
> ----------------------------------------------------------------
>
>                 Key: MNEMONIC-584
>                 URL: https://issues.apache.org/jira/browse/MNEMONIC-584
>             Project: Mnemonic
>          Issue Type: Improvement
>          Components: Build, Release
>    Affects Versions: 0.13.0
>            Reporter: Wang, Gang
>            Assignee: Wang, Gang
>            Priority: Major
>             Fix For: 0.13.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The release.sh mixed the processes of release candidate build and releasing with bump. there are some tricky issues without decoupling those 2 works.
> The improvement should explicitly allow release manager to issues 2 type of commands for them respectively, e.g.
>  
> {code:java}
> release.sh candidate <args>...  # this is for candidate build
> release.sh bump <args>... # this is for final releasing and bump version into a new version
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)