commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COMMONSSITE-111) [release-plugin] create mojo for release promotion in svn
Date Wed, 16 May 2018 21:38:00 GMT

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

Gary Gregory commented on COMMONSSITE-111:
------------------------------------------

Releasing out of Nexus is not painful and not error prone IMO: select your project and click
promote.

The pain is all the other steps, like getting your {{svnmucc}} command just so. Everything
is worse for a multi-module project of course. 

The first problem is one I am getting creating the VOTE.txt file: How do you know the URL
of the RC you just uploaded to Nexus? 

Please see my comment https://issues.apache.org/jira/browse/COMMONSSITE-112?focusedCommentId=16477767&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16477767



> [release-plugin] create mojo for release promotion in svn
> ---------------------------------------------------------
>
>                 Key: COMMONSSITE-111
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-111
>             Project: Commons All
>          Issue Type: Improvement
>            Reporter: Rob Tompkins
>            Assignee: Rob Tompkins
>            Priority: Major
>
> Currently we have to run a series of svn commands to promote releases. It would be nice
if the release plugin did this for us.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message