This tees off of a remark in the recent vote thread about the disruption to CI of pom releases.
I don't believe that we need the full ASF release voting process for our internal shared POMs. I reason as follows: The Apache release process creates a particular legal status for a body of code. This has certain advantages for users and developers. However, that assumes that there are users! However, these POMs are not intended for use by anything except other pieces of Maven (the global ASF pom might be an exception). Thus, they should be viewed as part of the releases of Maven itself and the components and plugins, not as independent releases. To build any of our user-visible components from source, you need to use the right parent POM (give our take our friend at Gentoo). Arguably, what we need here is a tweak to the source plugin, or some other plugin, that could sweep the chain of parents into 'the release', or at least enumerate them. We could then argue that, maven-release-plugin aside, the shared poms are formally 'released' when the components that use them are releases. If this argument holds water, the shared poms could be pushed via the maven-release-plugin via lazy consensus, and the CI problems go away. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
