Well the problem is that most users won't notice any "votes" or are able
to take action on it (e.g. because they can't run a custom build maven
on their CI easily).
I already have recommended that there should be a SNAPSHOT build on the
download-page with clear indication to the user to help testing these
snapshots, but for some strange ASF policy it is not allowed to promote
snapshots on the download page.
e.g. on Tycho we have quite some success with the strategy we have a
simple instructions here:
https://github.com/eclipse-tycho/tycho/wiki#getting-tycho-snapshots
and a lot of projects using at least an extra nightly-build to get
warned early if things change/break for them so most of the time we get
reports of regressions withing a few days and can often verify fixes
right after the snapshot is deployed as people simply restart their
builds and can report back if it is fixed.
Am 29.05.23 um 09:36 schrieb Romain Manni-Bucau:
Le lun. 29 mai 2023 à 09:03, Delany <delany.middle...@gmail.com> a écrit :
Since most issues (like this one) are discovered after release, what about
introducing a backward compatibility policy of "second-to-last"?
For example, a feature is introduced (with config value BRIEF) in 3.9.2
Then its decided in 3.9.3 to change it to something else (SUMMARY).
This should be allowed since 3.9.3 is within the "cool off period".
If that wasn't done then from 3.9.4 the usual process of deprecation can be
followed to remove it (with attendant bureaucracy).
For the kind of developers who always update to the latest, like myself,
this isn't a problem.
I have chosen to get the latest features with the tradeoff of having to
deal with new issues.
This way the window for change is widened to include real world scenarios
and one settles these sorts of issues sooner.
Delany
Hi, this is what the vote is done for, if we do then you'll probably want
to tackle people upgrading later too (so a range) or to majors too so,
IMHO, it is just moving the issue that people don't test their build with
the snapshots. For the cli we can surely write a command to help but will
not solve the actual build so, still IMHO, we should just encourage people
to test during the vote period and if they don't we can't help much except
trying to fix unexpected regressions ASAP.
On Sun, 28 May 2023 at 22:58, 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
