Hi, I'm happy with the current rule/process CTR and not sure we want to receive more notification emails... when someone creates a PR to fix a typo in some documentation/javadoc or some very easy changes.
We have enough experience to create a PR when really necessary. On Wed, 26 Jan 2022 at 05:46, Slawomir Jaranowski <s.jaranow...@gmail.com> wrote: > Hi, > > On the page "Apache Maven Project Roles" [1] we have paragraph > about Committers with: > > The Apache Maven project uses a Commit then Review policy and has a number > of conventions which should be followed. > > > Looks like Review then Commit policy is from svn time, so should be > refreshed or confirmed that is actual. > > When we want Review than Commit policy, we need some rules which allow us > to effectively work if nobody is interested for feedback. > We also need rules / examples for direct commits, when they are acceptable. > > Do we need different rules for Maven core, plugins, shared ... etc > > Example of rule: > > PR -> no feedback for X days -> send a mail on dev@, if still not feedback > after X days after mail -> proceed alone > > [1] https://maven.apache.org/project-roles.html#committers > > -- > Sławomir Jaranowski >
