Nope IIRC the intent of MENFORCER-267 is that the version should be 3.0.0 (hence the Fix Version)
On 20 June 2017 at 04:14, Anders Hammar <[email protected]> wrote: > v2.0.0? > > /Anders > > On Tue, Jun 20, 2017 at 12:53 PM, Stephen Connolly < > [email protected]> wrote: > > > Hmmm in reviewing the code provenance I notice that > > https://svn.apache.org/viewvc?view=revision&revision=1791757 was merged > > without bumping the pom version to 3.0.0. > > > > Should we drop and respin with 3.0.0 as the release version? > > > > Otherwise all looks good to me, but I'd rather get opinion on the version > > number in light of MENFORCER-267 having snuck in > > > > On 20 June 2017 at 02:02, Stephen Connolly <stephen.alan.connolly@gmail. > > com> > > wrote: > > > > > Hi, > > > > > > We solved 14 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > > projectId=12317520&version=12333353&styleName=Text > > > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20% > > > 3D%2012317520%20AND%20status%20%3D%20Open%20ORDER%20BY% > > > 20key%20DESC%2C%20priority%20DESC > > > > > > Staging repo: > > > https://repository.apache.org/content/repositories/maven-1342/ > > > https://repository.apache.org/content/repositories/maven- > > > 1342/org/apache/maven/enforcer/enforcer/1.4.2/ > > > enforcer-1.4.2-source-release.zip > > > > > > Source release checksum(s): > > > enforcer-1.4.2-source-release.zip-source-release.zip sha1: > > > 213f832f38529f02b38de6b7b2cc5804964e244f > > > > > > Staging site: > > > https://maven.apache.org/components/enforcer-archives/enforcer-LATEST/ > > > > > > Guide to testing staged releases: > > > https://maven.apache.org/guides/development/guide- > testing-releases.html > > > > > > Vote open for at least 72 hours. > > > > > > [ ] +1 > > > [ ] +0 > > > [ ] -1 > > > > > >
