[
https://issues.apache.org/jira/browse/MNGSITE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615099#comment-17615099
]
ASF GitHub Bot commented on MNGSITE-491:
----------------------------------------
cstamas commented on PR #321:
URL: https://github.com/apache/maven-site/pull/321#issuecomment-1273271125
And a LOT are yet to land to master, so I don't see why "a LOT of changes
present" implies "make it RTC". I don't see why we want to "hold back" the pace
of progress (as RTC does exactly that, holds back things, delays them), when
our interest would be exactly the opposite: make it happen the soon the better
(and this does not imply "chaos" re commits, hopefully).
Also, this is Maven https://github.com/apache/maven we talk about here, but
same does not apply to zillion of other Maven repositories.... for example
m-ear-p master or whatever...
> 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: Tamas Cservenak
> 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)
