[MRELEASE-1065] Workflow for maven-release-plugin for creating new release in branch

**[Peter Kronenberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterkronenberg)** opened **[MRELEASE-1065](https://issues.apache.org/jira/browse/MRELEASE-1065?redirect=false)** and commented

Hi, hope this is the right place for questions

I'm trying to figure out the proper workflow for creating a new release in a branch, but still setting the current branch for new development

Assuming I'm currently at release 1.0.5-SNAPSHOT. If I do **mvn release:prepare**, it correctly updates the version to 1.0.5, tags it, and then sets up for new development with 1.0.6-SNAPSHOT.

I want to do something similar with a new branch instead of tagging. My expectation would be the new branch would get 1.0.5 and the current branch would get 1.0.6-SNAPSHOT

Using the command

```java
mvn release:branch -DbranchName=1.0.5 -DreleaseVersion=1.0.5
```

I've tried variations of **-DupdateBranchVersions** and **-DupdateWorkingCopyVersions**. It doesn't appear to do what I want. I also can't seem to get **-DupdateVersionsToSnapshot=false** to work. It insists on naming the branch with Snapshot

Is there any way to do this?

---
No further details from [MRELEASE-1065](https://issues.apache.org/jira/browse/MRELEASE-1065?redirect=false)

Start with the maven-release-plugin's release:branch goal and the mentioned parameters: branchName, releaseVersion, updateBranchVersions, updateWorkingCopyVersions, and updateVersionsToSnapshot. Compare the documented workflow with the requested result: a release-version branch and a current branch set to the next SNAPSHOT version. Done requires determining whether this workflow is supported and documenting or implementing the required behavior.

Written by the indexing model from the issue text.