[MRELEASE-1140] New version suggestion should be based on previous release

**[Delany](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=delany)** opened **[MRELEASE-1140](https://issues.apache.org/jira/browse/MRELEASE-1140?redirect=false)** and commented

When i run **release:prepare** the plugin suggests what the new version should be.

On some of my projects it will suggest raising the minor version number, and on others it suggests raising the patch version number.

Judging from experience, the algorithm looks at the FIRST release I made for the project and will suggest that for eternity. So if for the first release I bumped the minor version number, it will suggest changing that even if the last 10 times I bumped the patch number, e.g.

```java
[INFO] 5/17 prepare:map-release-versions
What is the release version for "Thirdparty"? (thirdparty) 1.1.0: : 1.0.10 
[INFO] 6/17 prepare:input-variables
What is the SCM release tag or label for "Thirdparty"? (thirdparty) v1.0.10: : 
[INFO] 7/17 prepare:map-development-versions
What is the new development version for "Thirdparty"? (thirdparty) 1.1.0-SNAPSHOT: : 1.0.11-SNAPSHOT
```

This is inconvenient. I would be better if it considered the LAST release only. Perhaps there could be a configuration for this.

---

**Affects:** 3.0.1

Start by running the release:prepare flow and trace how it generates the suggested release and development versions. Compare the suggestions with the project's most recent release rather than its first release; done means repeated patch releases no longer cause an old minor-version suggestion, while the reported example remains understandable.

Written by the indexing model from the issue text.