[
https://issues.apache.org/jira/browse/MNGSITE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602263#comment-17602263
]
Tamás Cservenák edited comment on MNGSITE-491 at 9/9/22 11:08 AM:
------------------------------------------------------------------
Biggest problem: Curent maven site on page
[https://maven.apache.org/project-roles.html] contains this sentence: "The
Apache Maven project uses a Commit then Review policy [...]" which is not true.
Since more than 10 years (at least since migration from Subversion and
mirroring to GH) we started using GitHub PRs, and practice shows that we
actually do:
* CTR for trivial/simple changes
* RTC for complex changes or changes against stable branches
Stable branches in this moment are:
* maven-3.8.x reserved as bugfix branch (will be used to release a dot bugfix
version of Maven 3.8.x in case some blocker bug is reported (unlikely)
* maven-3.9.x is upcoming Maven 3.9.x version, and releases of Maven 3.9.x
line will happen from this branch (as Maven4 lives in parallel with 3.9.x)
* master is actually Maven4, and is a bit counterintuitive, but this is
exceptional case, that work on Maven4 and Maven 3.9 happens in parallel (I
don't remember so far it happened, that two major versions od Maven were worked
on simultaneously)
* all the other "older" family branches as well that were used for release
Ideally, if unsure, ask on dev ML about current set of "stable" branches.
was (Author: cstamas):
Biggest problem: Curent maven site on page
[https://maven.apache.org/project-roles.html] contains this sentence: "The
Apache Maven project uses a Commit then Review policy [...]" which is not true.
Since more than 10 years (at least since migration from Subversion and
mirroring to GH) we started using GitHub PRs, and practice shows that we
actually do:
* CTR for trivial/simple changes
* RTC for complex changes or changes against stable branches
Stable branches in this moment are:
* maven-3.8.x reserved as bugfix branch (will be used to release a dot bugfix
version of Maven 3.8.x in case some blocker bug is reported (unlikely)
* maven-3.9.x is upcoming Maven 3.9.x version, and releases of Maven 3.9.x
line will happen from this branch (as Maven4 lives in parallel with 3.9.x)
* master is actually Maven4, and is a bit counterintuitive, but this is
exceptional case, that work on Maven4 and Maven 3.9 happens in parallel (I
don't remember so far it happened, that two major versions od Maven were worked
on simultaneously)
* all the other "older" family branches as well that were used for release
(maven-3.6.x etc)
> Update commit policy related documents to avoid any misunderstanding
> --------------------------------------------------------------------
>
> Key: MNGSITE-491
> URL: https://issues.apache.org/jira/browse/MNGSITE-491
> Project: Maven Project Web Site
> Issue Type: Improvement
> Reporter: Tamás Cservenák
> Priority: Major
>
> Last update related to commit policies happened while project was still
> hosted in Subversion. Since then, a LOT of that changed (migrated to git,
> using Github.com, etc), so refresh the parts that are dated since Svn and are
> related to commit policies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
