The seemingly endless debate about Maven decamped from this list to a JIRA, and continued to be apparently endless. However, it seems to me that it really isn't all that far away from a reasonable resolution. The following is an attempt to summarize the decision points.
1: Should the Lucene PMC publish maven artifacts at all? - There seems to remain a consensus of the community: "Yes". 2: Should the publication be a seamless aspect of the release process, or a secondary step after the coast is clear? (And, if secondary, should snapshots be pushed automatically?) 3: Should the Lucene PMC ever take responsibility for distributing other people's stuff? This has been one of the more fraught questions, and needs to be divided up a bit. 3a: Should the PMC formally vote and release source of modified versions of other people's stuff, and in particular other Apache TLP's stuff? Keeping in mind strong guidance from the board to the effect that packages must be renamed in this case. 3b: Should the PMC include modified binaries that it creates in 'lib' directories or as Maven artifacts? (That is, advertise them for inclusion in users' application classpaths) Keeping in mind strong guidance from the board to the effect that packages must be renamed in this case. Also note that pulling in a binary from github or maven central is, I claim, noncontroversial. 3c: Should the PMC include modified binaries in binary release packages without advertising them for inclusion in users' application classpaths? Renaming is not required here, but the source release has to be buildable. - I think that the consensus here is 'yes'. 4: If the answer to some pieces of (3) is a 'no', should individuals of the Lucene PMC take steps to arrange for the convenient existence of releases of modified versions of other people's stuff? In thinking about item 4, I invite commentators to distinguish 'a bugfix that fixes a problem for some people some of the time' from 'a change that is absolutely necessary for the Lucene PMC release to work at all'. 5: Are there enough Maven-maven contributors to ensure that Maven-related issues are dealt with swiftly? 6: (Semi-seriously) are there enough Apache policy geek contributors to ensure that releases comply with policy, on all fronts ranging from the minutia of NOTICE files to the questions above under (3)? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
