[GitHub] [maven-site] cstamas commented on pull request #321: [MNGSITE-491] Update commit policy related document

[GitBox <gi...@apache.org>]

cstamas commented on PR #321:
URL: https://github.com/apache/maven-site/pull/321#issuecomment-1273252524

   Thanks for feedback, but am closing this PR as I have a feeling that this PR will not help, just mess things up, and these are the reasons:
   * PR can be created by "anybody" (whoever has a GH account), while doco assumes it is committer only
   * in theory I do agree that a code change can be delivered in any way (even with attaching it to JIRA), but only in theory. Personally, I find it very rare to review such a patch attachment, Today a GH pull request -- that I agree, is not "mandatory", but really a "nice thing to have" -- can be reviewed from a handheld, no need for checkout, workspace, IDE, etc.
   
   Moreover, my points were missed IMO, as (in this very moment when I write this comment): 
   * the maven-3.8.x branch should be RTC, it exists merely that in (very unlikely, but still) case of some nasty bug report against 3.8.6 force us to provide a patch/fix 3.8.7... IMHO, there should not land any other change,  as it can be easily seen, that it mayeven not produce any release  anymore (or in other words, we do not plan for 3.8.7, but we MAY be forced to make it).
   * the maven-3.9.x same thing: we are in few steps before "finish" line, we do plan a release of 3.9.0 in "near future" (was planned for Aug 2022, but heh).... for me, it is RTC only as well
   * master is CTR, as release of 4 is frankly, not happening in "near future"


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org