Re: GitHub issues - switching technical tasks

On Wed, 8 Jan 2025 at 21:41, Sylwester Lachiewicz wrote: > > Another thing that could be automated like labels - is the management of > .asf.yaml and README.md files for our repositories. > I see - READM.md - issues templates, PR templates and so on ... We can start a new thread about it. >

Re: GitHub issues - switching technical tasks

Another thing that could be automated like labels - is the management of .asf.yaml and README.md files for our repositories. Sylwester śr., 8 sty 2025 o 18:51 Sandra Parsick napisał(a): > I created for the mentioned Jira projects some test repositories that > show the migration result. > > > >>

Re: (maven-jarsigner-plugin) branch guice deleted (was 2c2510a)

Oh, and DO USE forks please, as then I will not have to nag anyone about cleaning up. T On Wed, Jan 8, 2025 at 9:03 PM Tamás Cservenák wrote: > > Please clean up after yourself, this should be done by a PR author. > > Thanks > T > > -- Forwarded message - > From: > Date: Wed, Ja

Fwd: (maven-jarsigner-plugin) branch guice deleted (was 2c2510a)

Please clean up after yourself, this should be done by a PR author. Thanks T -- Forwarded message - From: Date: Wed, Jan 8, 2025 at 9:01 PM Subject: (maven-jarsigner-plugin) branch guice deleted (was 2c2510a) To: comm...@maven.apache.org This is an automated email from the ASF

Re: GitHub issues - switching technical tasks

I created for the mentioned Jira projects some test repositories that show the migration result. - ARCHETYPE There is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I don't have time to support it so please someone else to help. If we want to copy release note

[VOTE] Release Apache Maven Artifact Plugin version 3.6.0

Hi, We solved 5 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324322&version=12355247&styleName=Text Staging repo: https://repository.apache.org/content/repositories/maven-2261/ https://repository.apache.org/content/repositories/maven-2261/org/apache/maven/plugins/mav

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

Bundling it all together seems like a much more effective way of doing it, though. It turns out that I already created an Issue when I started working on it last December. I thought that I’d had some kind of senior moment when I couldn’t find the Issues in the GitHub repo, but now I head back t

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

Also note that new enforcer rules do not have to ship with the plugin. There are many that are not bundled with the core plugin such as the extra-enforcer-rules and the Java Linkage checker rule

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

maven-enforcer-plugin has not yet migrated. Most projects haven't yet. See https://issues.apache.org/jira/projects/MENFORCER/issues/MENFORCER-473?filter=allopenissues On Wed, Jan 8, 2025 at 9:51 AM Andy Law wrote: > > …and then I realised that this relates to the “Migration from JIRA” thread… >

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

…and then I realised that this relates to the “Migration from JIRA” thread… From: Andy Law Date: Wednesday, 8 January 2025 at 09:35 To: Maven Developers List Subject: Re: Contributing a Pull Request for the enforcer plugin - branch etiquette That would be easier if there was an ‘Issues’ tab on

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

That would be easier if there was an ‘Issues’ tab on the apache/maven-enforcer repository. I presume the lack of that (plus ‘Discussions’ and ‘Wiki’ tabs) is a configuration thing. Can someone please fix that for me? Thanks in advance. Later, Andy From: Elliotte Rusty Harold Date: Tuesday,

Re: GitHub issues - switching technical tasks

On Wed, 8 Jan 2025 at 03:36, Hervé Boutemy wrote: > > we'll need to clarify what projects are guinea pigs, to stress test the > issues history copy > and releases/milestones > > I see 3 cited: > - ARCHETYPE There is a PR for ARCHETYPE - please review. After merge we can try to copy the issue - I