I don't care about the threads. They are fine with me. I care about the amount of ceremony that you create that eats into developer time. If you want to do it for yourself: feel free to do so. It is your time after all.
But you and others then turn around and say "everyone now needs to do what I am doing and you can no longer work the way that Apache always worked". And I object to that. There is value in ceremony for large, gnarly, critical changes that need discussion. And those should be approached very carefully and slowly. But having ceremony for a non-controversial, one line change that can be backed out easily if needed, is ceremony for ceremonies' sake. -h On Wed, May 31, 2023 at 4:23 AM Tamás Cservenák <ta...@cservenak.net> wrote: > Henning, > > This intent of all threads (the "[HEADS UP]") that I have been creating > since the 3.9.0 release was actually meant as a communication effort to > users not on ML (btw, see related comm related discussions). What I usually > do is copy the ponymail URL of the thread and post it on twitter or > mastodon etc. > People not on ML are still eager to be "in the loop", to get the news about > 3.9.x just like you might be. > > While I understand your frustration about these threads (probably noise to > you), please understand the intent behind these threads it as well. > > Thanks > T > > > > On Sun, May 28, 2023 at 10:58 PM Henning Schmiedehausen < > henn...@schmiedehausen.org> wrote: > > > You spend so much time on ceremony and bureaucracy by filing tickets that > > no one is going to pick up or read and then creating pull requests that > at > > best will be glanced at and then "LGTM"ed. > > > > This is a trivial, non-controversial change that any committer can just > > commit. Worst case scenario, someone else is going to comment on it and > > then it can be iterated. That is how Apache has always worked and why CTR > > is more efficient with a small team. Every committer is explicitly > trusted > > to work on the code base without constant "there needs to be a ticket. > > there needs to be a PR. there needs to be a week of discussion whether > that > > change is good. there needs to be "approval" or "majority agreement" by > > some star chamber that can decide what is good for the project. > > > > Reserve the ceremony and discussion for the large, gnarly, controversial > > changes that warrant discussion and where there is value in doing more > > upfront planning. But for god's sake, stop doing ceremony for ceremony's > > sake. > > > > It is a literal one-liner. - https://github.com/apache/maven/pull/1132 > > > > -h > > > > > > On Fri, May 26, 2023 at 1:24 PM Tamás Cservenák <ta...@cservenak.net> > > wrote: > > > > > Howdy, > > > > > > good call, created https://issues.apache.org/jira/browse/MNG-7797 > > > > > > Thanks > > > T > > > > > > On Fri, May 26, 2023 at 10:09 PM Henning Schmiedehausen < > > > henn...@schmiedehausen.org> wrote: > > > > > > > maven 3.9.2: > > > > > > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean > > > > install > > > > [...] > > > > > > > > current 3.9.3-SNAPSHOT: > > > > > > > > mvn -DskipTests -Dmaven.plugin.validation=BRIEF -pl :jdbi3-core clean > > > > install > > > > [...] > > > > > > > > *[WARNING] Invalid value specified for property > > maven.plugin.validation: > > > > 'BRIEF'. Supported values are (case insensitive): [NONE, INLINE, > > SUMMARY, > > > > VERBOSE]* > > > > > > > > You shipped "BRIEF" in 3.9.2, removing it now breaks scripts that > added > > > > this to the command line or the pom. > > > > > > > > I suggest mapping "BRIEF" to "SUMMARY". > > > > > > > > -h > > > > > > > > > > > > On Fri, May 26, 2023 at 12:46 AM Tamás Cservenák < > ta...@cservenak.net> > > > > wrote: > > > > > > > > > Howdy, > > > > > > > > > > Resolver 1.9.11 is shaping: > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.11 > > > > > > > > > > one resolver issue under scrutiny: > > > > > https://issues.apache.org/jira/browse/MRESOLVER-362 > > > > > > > > > > Maven 3.9.3 as well: > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.3 > > > > > > > > > > As usual, I plan these for next week, so if anyone has anything to > > say, > > > > > speak up! > > > > > > > > > > Thanks > > > > > T > > > > > > > > > > > > > > >