[MRELEASE-996] Staging a release cleans up

**[Ben Maes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ben-pensionarchitects)** opened **[MRELEASE-996](https://issues.apache.org/jira/browse/MRELEASE-996?redirect=false)** and commented

The wiki's documentation says the following about staging a release:

> After the release is complete, the release.properties and other release files will NOT be removed, so that you can still execute a release:rollback if some error has been detected and a new candidate must be created after some fixes. You just need to use a distinct tag in SCM, or rename the one that has been created if the SCM provider supports renaming tags.

Found in [usage](http://maven.apache.org/maven-release/maven-release-plugin/usage.html) on the bottom under staging a release

However everytime I use mvn release:stage the last thing showing up on my commandline is

> [INFO] Uploaded: http://devserver:8081/nexus/content/repositories/release_candidates/be/pensionarchitects/aatest/1.3.8/aatest-1.3.8-javadoc.jar (66 KB at 420.2 KB/sec)
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] BUILD SUCCESS
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Total time: 7.225 s
> [INFO] [INFO] Finished at: 2018-01-31T14:15:21+01:00
> [INFO] [INFO] Final Memory: 25M/310M
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] Cleaning up after release...
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 11.333 s
> [INFO] Finished at: 2018-01-31T14:15:21+01:00
> [INFO] Final Memory: 17M/310M
> [INFO] ------------------------------------------------------------------------

Thx

---

**Affects:** 2.5.3

Start by comparing the staging-release behavior described in the usage documentation with the output from mvn release:stage, especially the final cleanup step. Check whether release.properties and other release files remain available for release:rollback; done means the implementation and documentation agree on the expected cleanup behavior.

Written by the indexing model from the issue text.