I don't think that should be necessary. A failed 3.3.0 release should not use up the version number. I think there are instructions on the release page for unrolling a failed release, though I haven't had cause to use them myself.
On Fri, Jul 17, 2020 at 5:53 AM Dennis Lundberg <[email protected]> wrote: > > Hi again, > > While I was digging in VCS history I discovered something odd with > maven-shared-utils. The current trunk/head in git has version > 3.3.0-SNAPSHOT. But maven-shared-utils 3.3.0 was tagged during a release > in 2017... > https://github.com/apache/maven-shared-utils/tree/029ac4ec7b6636e8c1d3230799be624ba769e4cf/ > > After that release, work was done and a patch version 3.2.1 was released, > setting the next version to 3.2.2-SNAPSHOT. However that was recently > changed to 3.3.0-SNAPSHOT in > https://github.com/apache/maven-shared-utils/commit/87da81f880be3ad32080e4d2176e280958aff2d7 > > So, to avoid any potentially failed future release attempts I would like to > set the version to 3.4.0-SNAPSHOT, unless anyone objects. > > Someone who has worked on this component should have a look in JIRA, and > decide whether to mark the Release maven-shared-utils-3.3.0 as Released. > https://issues.apache.org/jira/projects/MSHARED/versions/12342756 > > -- > Dennis Lundberg -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
