Jason, your hyperbole has slipped again. There is no need to make assertions about how many or what kind of users other developers have worked with, as that both does not foster the community and deflects from the valid point you were otherwise making. Christian has done the right thing in seeking consensus before attempting to make a change in this area and what thanks does he get? Instead he gets trampled on because in the past he made breaking changes that would have had grave consequences. Do not trample on somebody for doing the wrong thing in the past when they are in the middle of doing the right thing! Jason, as to breaking changes in a minor version... does that mean we can revert the immutable model changes that broke lots of shade users builds?
Christian, this project has historically taken very seriously the goal of allowing users to upgrade Maven without breaking their existing builds. Whether we should continue to do so is a separate question, but certainly we cannot change mid-major version. I am still working on my proposal for a version 5 of Maven. I am proposing version 5 for two reasons: 1. It allows us to align the modelVersion with the Maven version 2. It gives space for behavioural changes before the big pom format change Now having said that, my proposal for Maven 5 is just *my* proposal. From the point of view of making a decision for the direction of this project my voice is just one voice amongst all the *committers*. It is the *committers* that decide the direction of this project - not the PMC. The PMC is responsible for governance and ensuring that releases meet the foundation's legal criteria established by the board. I am encouraged by the energy Christian is showing for this project, in part it has inspired me to put effort into describing my plan for a way forward. What we need to do right now is get 3.4.0 released. That means ensuring that the integration tests pass. In a separate part of this thread Igor reports that there are 24 tests not passing against master. Somebody needs to diagnose why those tests are failing. Some failures may require changes to the integration tests... some may require fixing the code. Let's figure out what the story is for those 24 tests. The point we need to remember about the goal for 3.4.0 is to be a release with the code formerly known as Aether moved to the Maven project and bug fixes applied to that code. We should keep our focus on that and try not to grow the scope... there are users clamouring for fixing that set of problems. Once we have the 3.4.x line then we should sit down and plan the path forward. -Stephen On 16 November 2016 at 05:44, Christian Schulte <c...@schulte.it> wrote: > To sum it up. I've asked the very same question a few weeks ago. That > has lead to creating that maven-3.x-next branch. A few weeks later I get > a different answer and that branch becomes obsolete and all JIRA issues > for version 3.5.0 need updating and the branch can be deleted, because > it became meaningless. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
