Re: GH issues and GH discussions

On Tue, 30 May 2023 at 01:44, Hervé Boutemy wrote: > > Le lundi 29 mai 2023, 13:50:58 CEST Karl Heinz Marbaise a écrit : > > To fulfill the formalism (also have documented the decision here on the > > ML) we should start simply a VOTE to get an in general decision about > > moving to GH-issues to

Re: GH issues and GH discussions

On Mon, 29 May 2023 at 21:51, Karl Heinz Marbaise wrote: > > Hi, > > I would suggest to create an umbrella project like: > > apache-maven-project > > on github and make it the central starting point for users... to ask > question (discussions) and optionally reroute them to the appropriate > githu

Re: GH issues and GH discussions

On Tue, 30 May 2023 at 00:04, Gary Gregory wrote: > > GH has the notion of "projects". Can't we use that? > this is something very different. It's used to be a sort of project version in where to add issues/PRs you want to be done to finalize the project/version. (as an example look how it is use

[CANCELED][VOTE] Release Maven Surefire version 3.1.1

I am canceling this vote: * While going through JIRA issues I have noticed that I missed to update the test report schema file which makes the code inconsistent to it * Give elharo@ some time work on dep updates * Review a few low hanging report fruits Will try to respin by end of week M ---

Re: [VOTE] Release Maven Surefire version 3.1.1

Am 2023-05-29 um 18:27 schrieb Elliotte Rusty Harold: 1. There are 42 open PRs including some dependabot ones. Can any of these be resolved quickly? I have a branch as PR 'update-dendencies', but one needs to verify every dep independently because some break the build. Time consuming, as for

Re: [VOTE] Release Maven Surefire version 3.1.1

1. There are 42 open PRs including some dependabot ones. Can any of these be resolved quickly? 2. At least a few assorted dependencies are not up to date. The dependencies that are declared seem out of sync with what is and isn't used. I'll send some PRs. 3, On my JDK 8 Mac 11.7.5 system `mvn -Pr

Re: GH issues and GH discussions

Le lundi 29 mai 2023, 13:50:58 CEST Karl Heinz Marbaise a écrit : > To fulfill the formalism (also have documented the decision here on the > ML) we should start simply a VOTE to get an in general decision about > moving to GH-issues to leave JIRA behind... (not about the details) that > can be don

Re: GH issues and GH discussions

Hi, On 29.05.23 15:50, Christoph Läubrich wrote: I must confess "another central project" do not feels right: 1) there already is a "central" one everyone can easily find if searching for "maven github": https://github.com/apache/maven/ That does not help here because that project is Maven it

[RESULT] [VOTE] Release Maven Project Info Reports Plugin version 3.4.4

Hi, The vote has passed with the following result: +1: Gabriel Belingueres, Sylwester Lachiewicz, Michael Osipov, Hervé Boutemy, tison PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release the board report. -

Re: GH issues and GH discussions

GH has the notion of "projects". Can't we use that? Gary On Mon, May 29, 2023, 09:50 Christoph Läubrich wrote: > I must confess "another central project" do not feels right: > > 1) there already is a "central" one everyone can easily find if > searching for "maven github": https://github.com/ap

Re: GH issues and GH discussions

I must confess "another central project" do not feels right: 1) there already is a "central" one everyone can easily find if searching for "maven github": https://github.com/apache/maven/ 2) for "subprojects" its usually better to discuss things close where the code is Please note that some f

Re: [VOTE] Release Maven Surefire version 3.1.1

+1, tested on several projects without issues Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn |

Re: GH issues and GH discussions

Hi, On 29.05.23 14:07, Michael Osipov wrote: Am 2023-05-29 um 13:50 schrieb Karl Heinz Marbaise: Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them

Re: GH issues and GH discussions

Am 2023-05-29 um 13:50 schrieb Karl Heinz Marbaise: Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them to the appropriate github repos... In gener

Re: [VOTE] Release Maven Surefire version 3.1.1

Hi, +1 from me. Kind regards Karl Heinz Marbaise On 28.05.23 23:24, Michael Osipov wrote: Hi, we solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12353266 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?

Re: GH issues and GH discussions

Hi, I would suggest to create an umbrella project like: apache-maven-project on github and make it the central starting point for users... to ask question (discussions) and optionally reroute them to the appropriate github repos... In general I agree to the tendency to use GH issues etc. inst

Re: [VOTE] Release Maven Surefire version 3.1.1

Am 2023-05-28 um 23:24 schrieb Michael Osipov: Hi, we solved 9 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12353266 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resoluti

Re: [HEADS UP] Upcoming Resolver and Maven releases

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 t

Re: [HEADS UP] Upcoming Resolver and Maven releases

Le lun. 29 mai 2023 à 09:03, Delany 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 ch

Re: [HEADS UP] Upcoming Resolver and Maven releases

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 allo