Hi Brian,
there was a long thread about this matter recently here :
https://issues.apache.org/jira/browse/LEGAL-654
AFAICT, the discusion was closed with a "it's just fine, it's
scafolding, not a package intended to be offered for public usage" (/me
rephrasing)
We *could* couple the parent POM release with another project release,
but the trouble is that you need to get past the SNAPSHOT to cut a
release, which means a parent POM release before the project release.
We may find another way, and in this case, I'm fine with coupling both
releases.
In any case, I have migrated the wiki to
https://directory.apache.org/top-level-mgmt.html, so if you'd like to
add some more info, please feel free to do it there instead of the wiki.
The page is available in https://github.com/apache/directory-site, more
specifically on
https://github.com/apache/directory-site/blob/master/source/top-level-mgmt.md
Thanks !
On 17/10/2023 18:37, Brian Demers wrote:
There was a bit of discussion in the Maven BoF last week at Community
Over Code on the topic of parent POM release processes.
This was a follow up to a thread on the board mailing list in September
"RFC: Releasing with lazy consensus".
TL;DR A few different projects have not been voting on parent pom
releases, and the debate was is this allowed.
I haven't seen a formal decision on the topic, but the consensus at the
BoF was that a vote is required when releasing a parent pom.
(Personally I have mixed feelings about this, I can see both sides of
this debate)
There was a recommendation to ease some of the burden/toil of this extra
release step, stage parent pom release and project release at the same
time, e.g.:
1. Stage the parent pom release (up to step 4 in:
https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy <https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy> )
2. Stage the sub-project
3. Call for a single vote containing the parent and sub-project.
4. Release staging repos (and move both artifacts to dist.apache.org
<http://dist.apache.org>)
5. Other release related tasks...
I can take a pass at updating the wiki
<https://cwiki.apache.org/confluence/display/DIRxDEV/Top+Level+Pom+Management+Policy> with this info, unless someone wants to suggest another option, or feels strongly about keeping the process the way it is.
Thoughts,
-Brian
--
*Emmanuel Lécharny* P. +33 (0)6 08 33 32 61
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
