On Thu, 6 Feb 2025 at 09:56, Herve Boutemy wrote:
>
> On 2025/02/06 08:25:44 Slawomir Jaranowski wrote:
> > On Thu, 6 Feb 2025 at 08:56, Hervé Boutemy wrote:
> > >
> > > can we work on scaling the Jira to GH Issues first before diving into all
> > > the
> >
> > What do you think about "scaling t
On 2025/02/06 08:25:44 Slawomir Jaranowski wrote:
> On Thu, 6 Feb 2025 at 08:56, Hervé Boutemy wrote:
> >
> > can we work on scaling the Jira to GH Issues first before diving into all
> > the
>
> What do you think about "scaling the Jira to GH Issues"?
where we are
https://cwiki.apache.org/conf
On Thu, 6 Feb 2025 at 08:56, Hervé Boutemy wrote:
>
> can we work on scaling the Jira to GH Issues first before diving into all the
What do you think about "scaling the Jira to GH Issues"?
> implications of Maven 3 vs Maven 4 compatibility topic?
>
> I feel we launch too much large scale and cri
can we work on scaling the Jira to GH Issues first before diving into all the
implications of Maven 3 vs Maven 4 compatibility topic?
I feel we launch too much large scale and critical topics in parallel
Regards,
Hervé
Le mardi 4 février 2025, 18:53:30 CET Slawomir Jaranowski a écrit :
> Hi,
>
Hi,
A little clarification on why I would like to do it ...
- try shared GitHub tools with multi-release plugin 4x and 3.x versions [1]
- do first release based on GitHub issue - to have a lesson what
should be updated in procedures [2]
- give posiility to use GitHub issues by user with more used
Hi,
I will be working on compiler, install, deploy plugins to prepare and
switch to GitHub issues ...
First I will fix release-drafter configuration such we maintain two version
- master for Maven 4.x
- branch for Maven 3.x
Probably I need disable jenkins on master due to missing Maven beta,
r
