Re: [DISCUSS] Enable GitHub issues and GitHub discussions

Le mar. 22 oct. 2024 à 19:13, Matt Nelson a écrit : > I think the user experience for everyone but the most active members may > regress by moving issues to GH. Maven has a lot of repositories(100+) and > almost as many jira projects. I'm never quite sure if I'm logging an issue > to the correct

Re: [DISCUSS] Project member emeritus policy change

+1 Agree. Not sure of special flag, getting back online will be as simple as sending an email to PMC list On Wed, 23 Oct 2024 at 15:45, Slawomir Jaranowski wrote: > > On Tue, 22 Oct 2024 at 21:43, Guillaume Nodet wrote: > > > > I think the idea is not to *remove* members. > > My understanding (a

Re: [DISCUSS] Project member emeritus policy change

On Tue, 22 Oct 2024 at 21:43, Guillaume Nodet wrote: > > I think the idea is not to *remove* members. > My understanding (at least, what I agree with) is to flag members as active > or not. I don't see an option to flag a user ... We can simply remove from the project and as requested we can add

[PR] Bump maven.version from 4.0.0-beta-4 to 4.0.0-beta-5 [maven-hocon-extension]

dependabot[bot] opened a new pull request, #12: URL: https://github.com/apache/maven-hocon-extension/pull/12 Bumps `maven.version` from 4.0.0-beta-4 to 4.0.0-beta-5. Updates `org.apache.maven:maven-api-spi` from 4.0.0-beta-4 to 4.0.0-beta-5 Updates `org.apache.maven:maven-api-core`

Re: [DISCUSS] Project member emeritus policy change

I think the idea is not to *remove* members. My understanding (at least, what I agree with) is to flag members as active or not. This would help having a better understanding of the community dynamics, as indicated in the original email. If we don't remove members, any inactive member can just be

Re: [DISCUSS] Project member emeritus policy change

-1 At least once I have personally brought a long dormant Maven PMC member out of hibernation to approve PRs and releases, and it was very helpful for moving the train along when active PMC members weren't interested enough in what my team was doing to review code and vote for releases. And now th

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

Most Apache projects are already mirrored on GitHub so I'm not sure mirroring on yet another service would make sense. It might confuse people even more. Maybe. Gary On Tue, Oct 22, 2024, 2:46 PM Delany wrote: > Maybe its me but I never got the hang of JQL so JIRA always been difficult > to fin

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

Maybe its me but I never got the hang of JQL so JIRA always been difficult to find stuff, not to mention it's dog slow. There was mention of GitHub's terms of service. Its not the only game in town though - what about Gitlab or even Gitea? I'm sure they'd appreciate being able to host project code

Re: [DISCUSS] Project member emeritus policy change

Le mar. 22 oct. 2024 à 19:31, Ralph Goers a écrit : > I would suggest that just responding on mailing lists count as well. It is > fairly easy to see if a user’s email shows up in any of the mailing lists. > This would also include GitHub commits, PRs, discussions, etc. since they > all generate

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

GitHub can be a pain with all the email it generates. However, I would think Maven would be the perfect project to use discussions and issues. Every maven plugin would have its discussions in its repo so following along with areas one is interested in could be much easier. This list would still

Re: [DISCUSS] Project member emeritus policy change

I would suggest that just responding on mailing lists count as well. It is fairly easy to see if a user’s email shows up in any of the mailing lists. This would also include GitHub commits, PRs, discussions, etc. since they all generate email to a list. Also - do you truly mean “emeritus” (remo

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

I think the user experience for everyone but the most active members may regress by moving issues to GH. Maven has a lot of repositories(100+) and almost as many jira projects. I'm never quite sure if I'm logging an issue to the correct jira project. And I suspect that federating out into 100+ diff

Re: [DISCUSS] Project member emeritus policy change

+1 (nb) (already read the thread on slack) Am 22.10.2024 um 18:17 schrieb Tamás Cservenák: Howdy, I would like to propose a project policy change (followed by implementation) regarding "emeritus" status of PMCs and members. Proposal: 1) IF a PMC member is inactive for 24 months (did NOT parti

[DISCUSS] Project member emeritus policy change

Howdy, I would like to propose a project policy change (followed by implementation) regarding "emeritus" status of PMCs and members. Proposal: 1) IF a PMC member is inactive for 24 months (did NOT participate in any VOTE [by casting binding vote] OR did not create any commit that ended up in the

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 while it stays forwarded to the list (dev@ only I guess) and we close jira projects to avoid 2 sources of truth (side effect being to update sites to reflect that project by project) Romain Manni-Bucau @rmannibucau | Blog |

[ANN] Apache Maven 4.0.0-beta-5 released

The Apache Maven team is pleased to announce the release of the Apache Maven 4.0.0-beta-5 WORD OF WARNING: there are big issues discovered in beta-5 post staging. Still, we wanted it on Central due to the latest v4 API changes. Apache Maven is a software project management and comprehension tool.

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 for moving to GH issues On Tue, Oct 22, 2024 at 4:53 PM Guillaume Nodet wrote: > > I'd like to start discussing opening (and eventually slowly switching) from > JIRA to GitHub issues. > > JIRA is a bit of a pain to use, even though we have some automatic links > done with PRs and such. Account

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 (nb) I like Github Issues more then the JIRA ones as esp. the formatting is far much more comfortable than in JIRA. I could also imagine that the project recieves more issues (I only hope for useful ones, but well there might be more useless too), due the fact that many people have an Github

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.15.1

+1 On Tue, Oct 22, 2024, 17:32 Slawomir Jaranowski wrote: > Hi, > > We solved 1 issue: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12355165 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.15.1

Am 2024-10-22 um 17:29 schrieb Slawomir Jaranowski: Hi, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12355165 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resol

[VOTE] Release Apache Maven Archiver version 3.6.3

Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354850 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=component%20%3D%20maven-archiver%20AND%20project%20%3D%20MSHARED%20AND%20resolution%20%3D

[VOTE] Release Apache Maven Dependency Analyzer version 1.15.1

Hi, We solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12355165 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20mav

[VOTE] Release Maven Checkstyle Plugin version 3.6.0

Hi, NOTE: Read the details on this release here: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack we solved 1 issue: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223&version=12355210 There are still a couple of issues left in JIRA: https://i

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

On Tue, 22 Oct 2024 at 17:02, Michael Osipov wrote: > > Am 2024-10-22 um 16:52 schrieb Guillaume Nodet: > > I'd like to start discussing opening (and eventually slowly switching) from > > JIRA to GitHub issues. > > > > JIRA is a bit of a pain to use, even though we have some automatic links > > do

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 We can start step by step from projects with a little number of open issues, e.g. all shared components. We already have done it for parents poms. On Tue, 22 Oct 2024 at 16:54, Guillaume Nodet wrote: > > I'd like to start discussing opening (and eventually slowly switching) from > JIRA to Gi

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

Am 2024-10-22 um 16:52 schrieb Guillaume Nodet: I'd like to start discussing opening (and eventually slowly switching) from JIRA to GitHub issues. JIRA is a bit of a pain to use, even though we have some automatic links done with PRs and such. Accounts need to be authorized to maintain the numbe

[VOTE] Release Maven JXR version 3.6.0

Hi, NOTE: Read the details on this release here: https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack we solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527&version=12355209 There are still a couple of issues left in JIRA: https://

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

+1 for killing jira From: Guillaume Nodet Sent: Tuesday, October 22, 2024 10:52:56 PM To: Maven Developers List Subject: [DISCUSS] Enable GitHub issues and GitHub discussions I'd like to start discussing opening (and eventually slowly switching) from JIRA to GitH

Re: [DISCUSS] Enable GitHub issues and GitHub discussions

Really, support for Markdown in issues would be a pain healer. I did spend 15 minutes trying to format an issue correctly because whenever you switch between "Visual" and "Text" mode, your {{ }} are mixed up ... That's really painful. Le mar. 22 oct. 2024 à 16:52, Guillaume Nodet a écrit : >

[VOTE] Release Maven Plugin Tools version 3.15.1

Hi, we solved 2 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820&version=12355207 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPLUGIN%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repo

[DISCUSS] Enable GitHub issues and GitHub discussions

I'd like to start discussing opening (and eventually slowly switching) from JIRA to GitHub issues. JIRA is a bit of a pain to use, even though we have some automatic links done with PRs and such. Accounts need to be authorized to maintain the number of external accounts low enough within the ASF,

[RESULT] [VOTE] Release Apache Maven 4.0.0-beta-5, respin 1

Howdy, The vote has passed with the following result: +1b: Guillaume, Slawomir, Maarten PMC quorum: reached I will promote the artifacts to the central repo, the source release ZIP file and add this release to the board report. Also will update the release notes with known issues. Thanks T -

Re: [VOTE] Release Maven Dependency Plugin version 3.8.1

+1 On Mon, Oct 21, 2024 at 5:32 PM Michael Osipov wrote: > > Hi, > > we solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12355206 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/projects/MDEP/issues > > Stag

[PR] Bump org.junit.jupiter:junit-jupiter from 5.11.2 to 5.11.3 [maven-xinclude-extension]

dependabot[bot] opened a new pull request, #11: URL: https://github.com/apache/maven-xinclude-extension/pull/11 Bumps [org.junit.jupiter:junit-jupiter](https://github.com/junit-team/junit5) from 5.11.2 to 5.11.3. Release notes Sourced from https://github.com/junit-team/junit5/rele

[PR] Bump org.apache.maven.plugins:maven-invoker-plugin from 3.8.0 to 3.8.1 [maven-xinclude-extension]

dependabot[bot] opened a new pull request, #10: URL: https://github.com/apache/maven-xinclude-extension/pull/10 Bumps [org.apache.maven.plugins:maven-invoker-plugin](https://github.com/apache/maven-invoker-plugin) from 3.8.0 to 3.8.1. Commits https://github.com/apache/maven-in

Re: [VOTE] Release Apache Maven 4.0.0-beta-5, respin 1

+1 Generally I am not a big fan of shipping with large known defects, but I agree having the feedback on the majority of the things that do work is important. I think it would be good if we added a few more sample projects to our IT suite that use Maven 4 features that are enabled through th

Re: [VOTE] Release Apache Maven 4.0.0-beta-5, respin 1

+1 On Sat, 19 Oct 2024 at 20:26, Tamás Cservenák wrote: > > Howdy, > > We solved 68 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12355075 > > There are still a couple of issues left in JIRA: > https://issues.apache.org/jira/issues/?jql=project%20%3D%