No worries. The main way to run things when you do a promotion is:

mvn -Duser.name=<your_user_name> -Prelease clean commons-release:clean-staging 
test package site deploy

or for dry run:

mvn -Duser.name=<your_user_name> -Prelease -Ptest-deploy clean 
commons-release:clean-staging test package site deploy

doing this should clean up the dist.apache.org <http://dist.apache.org/> dev 
staging directory if there’s anything there when you start the staging process.

-Rob

> On Mar 13, 2019, at 9:20 PM, Bruno P. Kinoshita <ki...@apache.org> wrote:
> 
> Was waiting for the release before start working on imaging RC3.
> Thanks Rob!
> Bruno
> 
> 
>    On Thursday, 14 March 2019, 2:17:43 pm NZDT, Rob Tompkins 
> <chtom...@apache.org> wrote:  
> 
> [This announcement is only going to the dev list.]
> 
> The Apache Commons Release Plugin team is pleased to announce the release of 
> Apache
> Commons Release Plugin 1.6.
> 
> The Apache Commons Release Plugin is a collection of Java based Maven mojos 
> for
> Apache Commons
> Release process. These mojos are intended to be used as a collection of steps 
> to
> be strung
> together for the purpose of removing the manual steps required to produce an
> Apache Commons Release.
> 
> List of changes:
> http://commons.apache.org/commons-release-plugin/changes-report.html
> 
> For complete information on Apache Commons Release Plugin, including
> instructions
> on how to submit bug reports,
> patches, or suggestions for improvement, see the Apache Apache Commons
> Release Plugin website:
> 
> http://commons.apache.org/commons-release-plugin/index.html
> 
> Cheers,
> -Rob
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to