I am now -1 on commit 1677765 chrisgwarp <scmVersion>1.9.5-SNAPSHOT</scmVersion>
from maven-release. Back in May, this made source changes to require an unreleased, incompatible, SCM version. Now I can't release release to fix a critical problem. Further, since it involves this level of API dependency, I think it requires the version fo In my view, if you make change like this, you are responsible for getting the dependency released in a timely fashion. if you can't you should make a branch. The general 3.0 project is an exception in which we all agreed to switch around. My understanding of the commit veto policy for the ASF as a whole is this: I've presented a _technical_ objection to the commit (it prevents releases of the plugin), so the author should revert it. If the author does not revert it, I will tomorrow. After all, it's still there in svn and can be remerged onto a new branch. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
