You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kie.apache.org by Alex Porcelli <al...@porcelli.me> on 2025/03/14 13:07:07 UTC
[PROPOSAL] Immediate 10.1.0 Release from main
In light of recent discussions and the challenges we've faced as a
community, I propose a pragmatic step forward: a short-term 10.1.0
release cut directly from the main.
While 10.0.0 was officially released in December, the branch for that
release was cut mid-last year, meaning that our current codebase has
significantly evolved since then. Given the substantial improvements
and fixes accumulated over the past months, I believe an immediate
10.1.0 release would provide tangible value to our user base.
This proposal puts our users first by ensuring they receive an updated
and more stable version without further delay.
With this in mind, I propose the following:
- Temporarily pausing the implementation of previously voted proposals
to allow time for a proper discussion on our bylaws and to give the
community space to heal from recent escalations.
- Focusing on delivering 10.1.0 as an incremental update that brings
our latest work to users sooner rather than later.
- Cutting the release branch early next week, assuming there is consensus.
I’m happy to take the lead in managing the release process and would
appreciate feedback on the proposal and the timing for branching.
I'm looking forward to hearing your thoughts.
-
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Kennedy Bowers <kb...@apache.org>.
I'd also like to add to my +1 and ask if there's anything I can do to help with any release-related tasks. I might need some guidance, but I'd like to learn about it, with the aim of becoming more involved in future releases.
On 2025/03/17 13:49:17 Kennedy Bowers wrote:
> +1
>
> On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > +1
> >
> > Thank you, Alex!
> >
> > Toshiya
> >
> > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
> > wrote:
> >
> > > Yep, go for it. +1
> > >
> > > --
> > > Jason Porter
> > > Software Engineer
> > > He/Him/His
> > >
> > > IBM
> > >
> > >
> > > From: Alex Porcelli <al...@porcelli.me>
> > > Date: Friday, March 14, 2025 at 07:07
> > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > In light of recent discussions and the challenges we've faced as a
> > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > release cut directly from the main.
> > >
> > > While 10.0.0 was officially released in December, the branch for that
> > > release was cut mid-last year, meaning that our current codebase has
> > > significantly evolved since then. Given the substantial improvements
> > > and fixes accumulated over the past months, I believe an immediate
> > > 10.1.0 release would provide tangible value to our user base.
> > >
> > > This proposal puts our users first by ensuring they receive an updated
> > > and more stable version without further delay.
> > >
> > > With this in mind, I propose the following:
> > >
> > > - Temporarily pausing the implementation of previously voted proposals
> > > to allow time for a proper discussion on our bylaws and to give the
> > > community space to heal from recent escalations.
> > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > our latest work to users sooner rather than later.
> > > - Cutting the release branch early next week, assuming there is consensus.
> > >
> > > I’m happy to take the lead in managing the release process and would
> > > appreciate feedback on the proposal and the timing for branching.
> > >
> > > I'm looking forward to hearing your thoughts.
> > >
> > > -
> > > Alex
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Tiago Bento <ti...@apache.org>.
+1 and count on me to help!
On Mon, Mar 17, 2025 at 11:42 AM Kennedy Bowers <kb...@apache.org> wrote:
>
> I'd also like to add to my +1 and ask if there's anything I can do to help with any release-related tasks. I might need some guidance, but I'd like to learn about it, with the aim of becoming more involved in future releases.
>
> On 2025/03/17 13:49:17 Kennedy Bowers wrote:
> > +1
> >
> > On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > > +1
> > >
> > > Thank you, Alex!
> > >
> > > Toshiya
> > >
> > > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
> > > wrote:
> > >
> > > > Yep, go for it. +1
> > > >
> > > > --
> > > > Jason Porter
> > > > Software Engineer
> > > > He/Him/His
> > > >
> > > > IBM
> > > >
> > > >
> > > > From: Alex Porcelli <al...@porcelli.me>
> > > > Date: Friday, March 14, 2025 at 07:07
> > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > > In light of recent discussions and the challenges we've faced as a
> > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > release cut directly from the main.
> > > >
> > > > While 10.0.0 was officially released in December, the branch for that
> > > > release was cut mid-last year, meaning that our current codebase has
> > > > significantly evolved since then. Given the substantial improvements
> > > > and fixes accumulated over the past months, I believe an immediate
> > > > 10.1.0 release would provide tangible value to our user base.
> > > >
> > > > This proposal puts our users first by ensuring they receive an updated
> > > > and more stable version without further delay.
> > > >
> > > > With this in mind, I propose the following:
> > > >
> > > > - Temporarily pausing the implementation of previously voted proposals
> > > > to allow time for a proper discussion on our bylaws and to give the
> > > > community space to heal from recent escalations.
> > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > our latest work to users sooner rather than later.
> > > > - Cutting the release branch early next week, assuming there is consensus.
> > > >
> > > > I’m happy to take the lead in managing the release process and would
> > > > appreciate feedback on the proposal and the timing for branching.
> > > >
> > > > I'm looking forward to hearing your thoughts.
> > > >
> > > > -
> > > > Alex
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Kennedy Bowers <kb...@apache.org>.
I'd also like to add to my +1 and ask if there's anything I can do to help with any release-related tasks. I might need some guidance, but I'd like to learn about it, with the aim of becoming more involved in future releases.
On 2025/03/17 13:49:17 Kennedy Bowers wrote:
> +1
>
> On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > +1
> >
> > Thank you, Alex!
> >
> > Toshiya
> >
> > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
> > wrote:
> >
> > > Yep, go for it. +1
> > >
> > > --
> > > Jason Porter
> > > Software Engineer
> > > He/Him/His
> > >
> > > IBM
> > >
> > >
> > > From: Alex Porcelli <al...@porcelli.me>
> > > Date: Friday, March 14, 2025 at 07:07
> > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > In light of recent discussions and the challenges we've faced as a
> > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > release cut directly from the main.
> > >
> > > While 10.0.0 was officially released in December, the branch for that
> > > release was cut mid-last year, meaning that our current codebase has
> > > significantly evolved since then. Given the substantial improvements
> > > and fixes accumulated over the past months, I believe an immediate
> > > 10.1.0 release would provide tangible value to our user base.
> > >
> > > This proposal puts our users first by ensuring they receive an updated
> > > and more stable version without further delay.
> > >
> > > With this in mind, I propose the following:
> > >
> > > - Temporarily pausing the implementation of previously voted proposals
> > > to allow time for a proper discussion on our bylaws and to give the
> > > community space to heal from recent escalations.
> > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > our latest work to users sooner rather than later.
> > > - Cutting the release branch early next week, assuming there is consensus.
> > >
> > > I’m happy to take the lead in managing the release process and would
> > > appreciate feedback on the proposal and the timing for branching.
> > >
> > > I'm looking forward to hearing your thoughts.
> > >
> > > -
> > > Alex
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
After a second thought, I'm postponing the branching for tomorrow
morning. So it should give everyone here a relatively decent time to
wrap up anything. (Assuming that we won't try to rush a `new thing`)
On Mon, Mar 17, 2025 at 11:14 AM Thiago Lugli <th...@apache.org> wrote:
>
> +1
>
> Also, let me know how I can help with this release.
>
> Em seg., 17 de mar. de 2025 às 11:58, Alex Porcelli
> <po...@apache.org> escreveu:
> >
> > Francisco,
> >
> > Giving the overwhelming +1 and no suggestion for a specific point to
> > branch, I’m planning to branch today afternoon.
> >
> >
> > -
> > Alex
> >
> > On Mon, Mar 17, 2025 at 9:52 AM Francisco Javier Tirado Sarti
> > <ft...@redhat.com.invalid> wrote:
> >
> > > +1
> > > Please let us know when the cut is expected to happen (if possible with 24
> > > hours of notice ;)))
> > >
> > > On Mon, Mar 17, 2025 at 2:49 PM Kennedy Bowers <kb...@apache.org> wrote:
> > >
> > > > +1
> > > >
> > > > On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > > > > +1
> > > > >
> > > > > Thank you, Alex!
> > > > >
> > > > > Toshiya
> > > > >
> > > > > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jporter@ibm.com.invalid
> > > >
> > > > > wrote:
> > > > >
> > > > > > Yep, go for it. +1
> > > > > >
> > > > > > --
> > > > > > Jason Porter
> > > > > > Software Engineer
> > > > > > He/Him/His
> > > > > >
> > > > > > IBM
> > > > > >
> > > > > >
> > > > > > From: Alex Porcelli <al...@porcelli.me>
> > > > > > Date: Friday, March 14, 2025 at 07:07
> > > > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > > > > In light of recent discussions and the challenges we've faced as a
> > > > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > > > release cut directly from the main.
> > > > > >
> > > > > > While 10.0.0 was officially released in December, the branch for that
> > > > > > release was cut mid-last year, meaning that our current codebase has
> > > > > > significantly evolved since then. Given the substantial improvements
> > > > > > and fixes accumulated over the past months, I believe an immediate
> > > > > > 10.1.0 release would provide tangible value to our user base.
> > > > > >
> > > > > > This proposal puts our users first by ensuring they receive an
> > > updated
> > > > > > and more stable version without further delay.
> > > > > >
> > > > > > With this in mind, I propose the following:
> > > > > >
> > > > > > - Temporarily pausing the implementation of previously voted
> > > proposals
> > > > > > to allow time for a proper discussion on our bylaws and to give the
> > > > > > community space to heal from recent escalations.
> > > > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > > > our latest work to users sooner rather than later.
> > > > > > - Cutting the release branch early next week, assuming there is
> > > > consensus.
> > > > > >
> > > > > > I’m happy to take the lead in managing the release process and would
> > > > > > appreciate feedback on the proposal and the timing for branching.
> > > > > >
> > > > > > I'm looking forward to hearing your thoughts.
> > > > > >
> > > > > > -
> > > > > > Alex
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > >
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > >
> > > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Thiago Lugli <th...@apache.org>.
+1
Also, let me know how I can help with this release.
Em seg., 17 de mar. de 2025 às 11:58, Alex Porcelli
<po...@apache.org> escreveu:
>
> Francisco,
>
> Giving the overwhelming +1 and no suggestion for a specific point to
> branch, I’m planning to branch today afternoon.
>
>
> -
> Alex
>
> On Mon, Mar 17, 2025 at 9:52 AM Francisco Javier Tirado Sarti
> <ft...@redhat.com.invalid> wrote:
>
> > +1
> > Please let us know when the cut is expected to happen (if possible with 24
> > hours of notice ;)))
> >
> > On Mon, Mar 17, 2025 at 2:49 PM Kennedy Bowers <kb...@apache.org> wrote:
> >
> > > +1
> > >
> > > On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > > > +1
> > > >
> > > > Thank you, Alex!
> > > >
> > > > Toshiya
> > > >
> > > > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jporter@ibm.com.invalid
> > >
> > > > wrote:
> > > >
> > > > > Yep, go for it. +1
> > > > >
> > > > > --
> > > > > Jason Porter
> > > > > Software Engineer
> > > > > He/Him/His
> > > > >
> > > > > IBM
> > > > >
> > > > >
> > > > > From: Alex Porcelli <al...@porcelli.me>
> > > > > Date: Friday, March 14, 2025 at 07:07
> > > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > > > In light of recent discussions and the challenges we've faced as a
> > > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > > release cut directly from the main.
> > > > >
> > > > > While 10.0.0 was officially released in December, the branch for that
> > > > > release was cut mid-last year, meaning that our current codebase has
> > > > > significantly evolved since then. Given the substantial improvements
> > > > > and fixes accumulated over the past months, I believe an immediate
> > > > > 10.1.0 release would provide tangible value to our user base.
> > > > >
> > > > > This proposal puts our users first by ensuring they receive an
> > updated
> > > > > and more stable version without further delay.
> > > > >
> > > > > With this in mind, I propose the following:
> > > > >
> > > > > - Temporarily pausing the implementation of previously voted
> > proposals
> > > > > to allow time for a proper discussion on our bylaws and to give the
> > > > > community space to heal from recent escalations.
> > > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > > our latest work to users sooner rather than later.
> > > > > - Cutting the release branch early next week, assuming there is
> > > consensus.
> > > > >
> > > > > I’m happy to take the lead in managing the release process and would
> > > > > appreciate feedback on the proposal and the timing for branching.
> > > > >
> > > > > I'm looking forward to hearing your thoughts.
> > > > >
> > > > > -
> > > > > Alex
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> > >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <po...@apache.org>.
Francisco,
Giving the overwhelming +1 and no suggestion for a specific point to
branch, I’m planning to branch today afternoon.
-
Alex
On Mon, Mar 17, 2025 at 9:52 AM Francisco Javier Tirado Sarti
<ft...@redhat.com.invalid> wrote:
> +1
> Please let us know when the cut is expected to happen (if possible with 24
> hours of notice ;)))
>
> On Mon, Mar 17, 2025 at 2:49 PM Kennedy Bowers <kb...@apache.org> wrote:
>
> > +1
> >
> > On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > > +1
> > >
> > > Thank you, Alex!
> > >
> > > Toshiya
> > >
> > > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jporter@ibm.com.invalid
> >
> > > wrote:
> > >
> > > > Yep, go for it. +1
> > > >
> > > > --
> > > > Jason Porter
> > > > Software Engineer
> > > > He/Him/His
> > > >
> > > > IBM
> > > >
> > > >
> > > > From: Alex Porcelli <al...@porcelli.me>
> > > > Date: Friday, March 14, 2025 at 07:07
> > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > > In light of recent discussions and the challenges we've faced as a
> > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > release cut directly from the main.
> > > >
> > > > While 10.0.0 was officially released in December, the branch for that
> > > > release was cut mid-last year, meaning that our current codebase has
> > > > significantly evolved since then. Given the substantial improvements
> > > > and fixes accumulated over the past months, I believe an immediate
> > > > 10.1.0 release would provide tangible value to our user base.
> > > >
> > > > This proposal puts our users first by ensuring they receive an
> updated
> > > > and more stable version without further delay.
> > > >
> > > > With this in mind, I propose the following:
> > > >
> > > > - Temporarily pausing the implementation of previously voted
> proposals
> > > > to allow time for a proper discussion on our bylaws and to give the
> > > > community space to heal from recent escalations.
> > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > our latest work to users sooner rather than later.
> > > > - Cutting the release branch early next week, assuming there is
> > consensus.
> > > >
> > > > I’m happy to take the lead in managing the release process and would
> > > > appreciate feedback on the proposal and the timing for branching.
> > > >
> > > > I'm looking forward to hearing your thoughts.
> > > >
> > > > -
> > > > Alex
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Francisco Javier Tirado Sarti <ft...@redhat.com.INVALID>.
+1
Please let us know when the cut is expected to happen (if possible with 24
hours of notice ;)))
On Mon, Mar 17, 2025 at 2:49 PM Kennedy Bowers <kb...@apache.org> wrote:
> +1
>
> On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> > +1
> >
> > Thank you, Alex!
> >
> > Toshiya
> >
> > On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
> > wrote:
> >
> > > Yep, go for it. +1
> > >
> > > --
> > > Jason Porter
> > > Software Engineer
> > > He/Him/His
> > >
> > > IBM
> > >
> > >
> > > From: Alex Porcelli <al...@porcelli.me>
> > > Date: Friday, March 14, 2025 at 07:07
> > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > > In light of recent discussions and the challenges we've faced as a
> > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > release cut directly from the main.
> > >
> > > While 10.0.0 was officially released in December, the branch for that
> > > release was cut mid-last year, meaning that our current codebase has
> > > significantly evolved since then. Given the substantial improvements
> > > and fixes accumulated over the past months, I believe an immediate
> > > 10.1.0 release would provide tangible value to our user base.
> > >
> > > This proposal puts our users first by ensuring they receive an updated
> > > and more stable version without further delay.
> > >
> > > With this in mind, I propose the following:
> > >
> > > - Temporarily pausing the implementation of previously voted proposals
> > > to allow time for a proper discussion on our bylaws and to give the
> > > community space to heal from recent escalations.
> > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > our latest work to users sooner rather than later.
> > > - Cutting the release branch early next week, assuming there is
> consensus.
> > >
> > > I’m happy to take the lead in managing the release process and would
> > > appreciate feedback on the proposal and the timing for branching.
> > >
> > > I'm looking forward to hearing your thoughts.
> > >
> > > -
> > > Alex
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Kennedy Bowers <kb...@apache.org>.
+1
On 2025/03/17 03:08:02 Toshiya Kobayashi wrote:
> +1
>
> Thank you, Alex!
>
> Toshiya
>
> On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
> wrote:
>
> > Yep, go for it. +1
> >
> > --
> > Jason Porter
> > Software Engineer
> > He/Him/His
> >
> > IBM
> >
> >
> > From: Alex Porcelli <al...@porcelli.me>
> > Date: Friday, March 14, 2025 at 07:07
> > To: dev@kie.apache.org <de...@kie.apache.org>
> > Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> > In light of recent discussions and the challenges we've faced as a
> > community, I propose a pragmatic step forward: a short-term 10.1.0
> > release cut directly from the main.
> >
> > While 10.0.0 was officially released in December, the branch for that
> > release was cut mid-last year, meaning that our current codebase has
> > significantly evolved since then. Given the substantial improvements
> > and fixes accumulated over the past months, I believe an immediate
> > 10.1.0 release would provide tangible value to our user base.
> >
> > This proposal puts our users first by ensuring they receive an updated
> > and more stable version without further delay.
> >
> > With this in mind, I propose the following:
> >
> > - Temporarily pausing the implementation of previously voted proposals
> > to allow time for a proper discussion on our bylaws and to give the
> > community space to heal from recent escalations.
> > - Focusing on delivering 10.1.0 as an incremental update that brings
> > our latest work to users sooner rather than later.
> > - Cutting the release branch early next week, assuming there is consensus.
> >
> > I’m happy to take the lead in managing the release process and would
> > appreciate feedback on the proposal and the timing for branching.
> >
> > I'm looking forward to hearing your thoughts.
> >
> > -
> > Alex
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Toshiya Kobayashi <to...@gmail.com>.
+1
Thank you, Alex!
Toshiya
On Sat, Mar 15, 2025 at 12:56 AM Jason Porter <jp...@ibm.com.invalid>
wrote:
> Yep, go for it. +1
>
> --
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
>
> From: Alex Porcelli <al...@porcelli.me>
> Date: Friday, March 14, 2025 at 07:07
> To: dev@kie.apache.org <de...@kie.apache.org>
> Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Jason Porter <jp...@ibm.com.INVALID>.
Yep, go for it. +1
--
Jason Porter
Software Engineer
He/Him/His
IBM
From: Alex Porcelli <al...@porcelli.me>
Date: Friday, March 14, 2025 at 07:07
To: dev@kie.apache.org <de...@kie.apache.org>
Subject: [EXTERNAL] [PROPOSAL] Immediate 10.1.0 Release from main
In light of recent discussions and the challenges we've faced as a
community, I propose a pragmatic step forward: a short-term 10.1.0
release cut directly from the main.
While 10.0.0 was officially released in December, the branch for that
release was cut mid-last year, meaning that our current codebase has
significantly evolved since then. Given the substantial improvements
and fixes accumulated over the past months, I believe an immediate
10.1.0 release would provide tangible value to our user base.
This proposal puts our users first by ensuring they receive an updated
and more stable version without further delay.
With this in mind, I propose the following:
- Temporarily pausing the implementation of previously voted proposals
to allow time for a proper discussion on our bylaws and to give the
community space to heal from recent escalations.
- Focusing on delivering 10.1.0 as an incremental update that brings
our latest work to users sooner rather than later.
- Cutting the release branch early next week, assuming there is consensus.
I’m happy to take the lead in managing the release process and would
appreciate feedback on the proposal and the timing for branching.
I'm looking forward to hearing your thoughts.
-
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by "Pere Fernandez (apache)" <pe...@apache.org>.
+1
On Fri, 14 Mar 2025 at 15:52, Paolo Bizzarri <pi...@gmail.com> wrote:
> +1. I really appreciate this proposal. Thank you Alex.
>
> On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
>
> > In light of recent discussions and the challenges we've faced as a
> > community, I propose a pragmatic step forward: a short-term 10.1.0
> > release cut directly from the main.
> >
> > While 10.0.0 was officially released in December, the branch for that
> > release was cut mid-last year, meaning that our current codebase has
> > significantly evolved since then. Given the substantial improvements
> > and fixes accumulated over the past months, I believe an immediate
> > 10.1.0 release would provide tangible value to our user base.
> >
> > This proposal puts our users first by ensuring they receive an updated
> > and more stable version without further delay.
> >
> > With this in mind, I propose the following:
> >
> > - Temporarily pausing the implementation of previously voted proposals
> > to allow time for a proper discussion on our bylaws and to give the
> > community space to heal from recent escalations.
> > - Focusing on delivering 10.1.0 as an incremental update that brings
> > our latest work to users sooner rather than later.
> > - Cutting the release branch early next week, assuming there is
> consensus.
> >
> > I’m happy to take the lead in managing the release process and would
> > appreciate feedback on the proposal and the timing for branching.
> >
> > I'm looking forward to hearing your thoughts.
> >
> > -
> > Alex
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Paolo Bizzarri <pi...@gmail.com>.
+1. I really appreciate this proposal. Thank you Alex.
On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Tibor Zimányi <tz...@apache.org>.
Hi,
+1.
Thank you,
Tibor
Dňa pi 14. 3. 2025, 14:07 Alex Porcelli <al...@porcelli.me> napísal(a):
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Fabrizio Antonangeli <fa...@apache.org>.
+1
On Fri, 2025-03-14 at 15:47 +0200, Toni Rikkola wrote:
> +1 for release. It has been long enough since the last one came out.
>
> Toni
>
> On Fri, Mar 14, 2025 at 3:14 PM Alex Porcelli <al...@porcelli.me>
> wrote:
>
> > In light of recent discussions and the challenges we've faced as a
> > community, I propose a pragmatic step forward: a short-term 10.1.0
> > release cut directly from the main.
> >
> > While 10.0.0 was officially released in December, the branch for
> > that
> > release was cut mid-last year, meaning that our current codebase
> > has
> > significantly evolved since then. Given the substantial
> > improvements
> > and fixes accumulated over the past months, I believe an immediate
> > 10.1.0 release would provide tangible value to our user base.
> >
> > This proposal puts our users first by ensuring they receive an
> > updated
> > and more stable version without further delay.
> >
> > With this in mind, I propose the following:
> >
> > - Temporarily pausing the implementation of previously voted
> > proposals
> > to allow time for a proper discussion on our bylaws and to give the
> > community space to heal from recent escalations.
> > - Focusing on delivering 10.1.0 as an incremental update that
> > brings
> > our latest work to users sooner rather than later.
> > - Cutting the release branch early next week, assuming there is
> > consensus.
> >
> > I’m happy to take the lead in managing the release process and
> > would
> > appreciate feedback on the proposal and the timing for branching.
> >
> > I'm looking forward to hearing your thoughts.
> >
> > -
> > Alex
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Toni Rikkola <tr...@redhat.com>.
+1 for release. It has been long enough since the last one came out.
Toni
On Fri, Mar 14, 2025 at 3:14 PM Alex Porcelli <al...@porcelli.me> wrote:
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Yeser Amer <ya...@apache.org>.
+1
On 2025/03/14 13:07:07 Alex Porcelli wrote:
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@gmail.com>.
Update here,
It has been quite a work, all pipelines in KIE Tools are being revisited and adjusted. There are about 30 and something of those. Here you can see code adjustments activities in GitHub [1]. Hopefully we get it done soon and can continue with the release.
[1] - https://github.com/apache/incubator-kie-tools/commits/10.1.x/ [https://github.com/apache/incubator-kie-tools/commits/10.1.x/]
On 5/6/2025 8:07:46 PM, Alex Porcelli <po...@apache.org> wrote:
After 10.0.0 important changes happened in codebase with deep impact on KIE tools pipelines.
Things like new image (db-migration), new accelerator embedded in KIE tools repo, and the removal do Kogito images repo… is requiring a lot of review and code changes in pipelines.
This might take longer than originally planned.
-
Alex
On Sun, May 4, 2025 at 11:46 AM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]> wrote:
Quick update.
At this point I already have in staging all runtimes, however the release pipelines in Jenkins for all KIE Tools are completely broken.
They need a complete througout review. Eduardo and Tiago volunteered to help review. Given individuals agenda, we’ll meet to work on this next Tuesday end of the day (eastern time)
Regards,
_____________
Alex Porcelli
http://porcelli.me [http://porcelli.me]
On Wed, Apr 30, 2025 at 10:24 AM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]> wrote:
Thank you, Toshiya!
Drools build started!
On Wed, Apr 30, 2025 at 12:14 AM Toshiya Kobayashi
<toshiyakobayashi@gmail.com [mailto:toshiyakobayashi@gmail.com]> wrote:
>
> Thank you, Alex.
>
> I'm looking at the drools test failure and filed a fix PR :
> https://github.com/apache/incubator-kie-drools/pull/6328 [https://github.com/apache/incubator-kie-drools/pull/6328]
>
> Toshiya
>
>
> On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]> wrote:
>
> > Since yesterday a new attempt to release is in progress.
> >
> > The good news: after fighting with pipelines, the 10.1.x branches are
> > correctly created and with the proper version in place.
> >
> > However, I suspect there's a build failure in Drools and looks like a
> > legitimate issue, this came up during the docs removal PR [1]. I'd
> > appreciate it if any Drools SME could double check before proceeding
> > with the release.
> >
> > [1] - https://github.com/apache/incubator-kie-drools/pull/6327 [https://github.com/apache/incubator-kie-drools/pull/6327]
> >
> > On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]> wrote:
> > >
> > > Hi Team,
> > >
> > > Just a quick update - unfortunately, I discovered today that the
> > > branching pipelines for Kogito have failed, resulting in the 10.1.x
> > > branches being created with the 999-SNAPSHOT version in a few
> > > repositories (runtimes and apps)
> > >
> > > I attempted to re-run the pipeline, but unfortunately, that didn’t
> > > resolve the issue. At this point, I'm considering manually pushing the
> > > version update. The alternative would be to ask Apache Infra to delete
> > > the branches across all repositories so we can create a new weekly
> > > build, sync with KIE Tools, and restart the branching process from
> > > scratch.
> > >
> > > I’ll revisit this on Monday, as I have a planned day off tomorrow.
> > >
> > > -
> > > Alex
> > >
> > > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Just a quick update: all Jenkins release pipelines are currently
> > > > outdated and non-functional. During the 10.0.0 release, several
> > > > changes were made to the pipelines that were never fully brought back
> > > > to main. Additionally, some modifications exist only on main and were
> > > > not applied consistently across the different release branches.
> > > >
> > > > As a result, I'm currently working through each pipeline, resolving a
> > > > number of conflicts and inconsistencies to bring them back into sync.
> > > > This has proven to be quite time-consuming.
> > > >
> > > > Full transparency: I'm doing some direct commits/pushes for those
> > > > isolated CI-related changes to the 10.1.x branch. Much of this work
> > > > involves trial and error due to the lack of a local Jenkins
> > > > environment that mirrors Apache's setup. Requiring PR reviews for
> > > > every small change would significantly slow down progress and make an
> > > > already complex task even harder.
> > > >
> > > > I’ll keep you posted as things evolve.
> > > >
> > > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> > > > <ricardozanini@gmail.com [mailto:ricardozanini@gmail.com]> wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]>
> > wrote:
> > > > >
> > > > > > Quick update, the release repositories have been branched.
> > > > > >
> > > > > > For more dynamic updates, we have a topic [1] in Zulip.
> > > > > >
> > > > > > [1] -
> > > > > >
> > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread [https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread]
> > > > > >
> > > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pibizza@gmail.com [mailto:pibizza@gmail.com]>
> > wrote:
> > > > > > >
> > > > > > > As said by others, happy to learn and help here.
> > > > > > >
> > > > > > > Regards
> > > > > > >
> > > > > > > P.
> > > > > > >
> > > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <alex@porcelli.me [mailto:alex@porcelli.me]>
> > wrote:
> > > > > > >
> > > > > > > > In light of recent discussions and the challenges we've faced
> > as a
> > > > > > > > community, I propose a pragmatic step forward: a short-term
> > 10.1.0
> > > > > > > > release cut directly from the main.
> > > > > > > >
> > > > > > > > While 10.0.0 was officially released in December, the branch
> > for that
> > > > > > > > release was cut mid-last year, meaning that our current
> > codebase has
> > > > > > > > significantly evolved since then. Given the substantial
> > improvements
> > > > > > > > and fixes accumulated over the past months, I believe an
> > immediate
> > > > > > > > 10.1.0 release would provide tangible value to our user base.
> > > > > > > >
> > > > > > > > This proposal puts our users first by ensuring they receive an
> > updated
> > > > > > > > and more stable version without further delay.
> > > > > > > >
> > > > > > > > With this in mind, I propose the following:
> > > > > > > >
> > > > > > > > - Temporarily pausing the implementation of previously voted
> > proposals
> > > > > > > > to allow time for a proper discussion on our bylaws and to
> > give the
> > > > > > > > community space to heal from recent escalations.
> > > > > > > > - Focusing on delivering 10.1.0 as an incremental update that
> > brings
> > > > > > > > our latest work to users sooner rather than later.
> > > > > > > > - Cutting the release branch early next week, assuming there is
> > > > > > consensus.
> > > > > > > >
> > > > > > > > I’m happy to take the lead in managing the release process and
> > would
> > > > > > > > appreciate feedback on the proposal and the timing for
> > branching.
> > > > > > > >
> > > > > > > > I'm looking forward to hearing your thoughts.
> > > > > > > >
> > > > > > > > -
> > > > > > > > Alex
> > > > > > > >
> > > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org [mailto:dev-unsubscribe@kie.apache.org]
> > > > > > > > For additional commands, e-mail: dev-help@kie.apache.org [mailto:dev-help@kie.apache.org]
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org [mailto:dev-unsubscribe@kie.apache.org]
> > > > > > For additional commands, e-mail: dev-help@kie.apache.org [mailto:dev-help@kie.apache.org]
> > > > > >
> > > > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org [mailto:dev-unsubscribe@kie.apache.org]
> > For additional commands, e-mail: dev-help@kie.apache.org [mailto:dev-help@kie.apache.org]
> >
> >
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <po...@apache.org>.
After 10.0.0 important changes happened in codebase with deep impact on KIE
tools pipelines.
Things like new image (db-migration), new accelerator embedded in KIE tools
repo, and the removal do Kogito images repo… is requiring a lot of review
and code changes in pipelines.
This might take longer than originally planned.
-
Alex
On Sun, May 4, 2025 at 11:46 AM Alex Porcelli <al...@porcelli.me> wrote:
> Quick update.
>
> At this point I already have in staging all runtimes, however the release
> pipelines in Jenkins for all KIE Tools are completely broken.
>
> They need a complete througout review. Eduardo and Tiago volunteered to
> help review. Given individuals agenda, we’ll meet to work on this next
> Tuesday end of the day (eastern time)
>
> Regards,
> _____________
>
> Alex Porcelli
> http://porcelli.me
>
>
> On Wed, Apr 30, 2025 at 10:24 AM Alex Porcelli <al...@porcelli.me> wrote:
>
>> Thank you, Toshiya!
>>
>> Drools build started!
>>
>> On Wed, Apr 30, 2025 at 12:14 AM Toshiya Kobayashi
>> <to...@gmail.com> wrote:
>> >
>> > Thank you, Alex.
>> >
>> > I'm looking at the drools test failure and filed a fix PR :
>> > https://github.com/apache/incubator-kie-drools/pull/6328
>> >
>> > Toshiya
>> >
>> >
>> > On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <al...@porcelli.me> wrote:
>> >
>> > > Since yesterday a new attempt to release is in progress.
>> > >
>> > > The good news: after fighting with pipelines, the 10.1.x branches are
>> > > correctly created and with the proper version in place.
>> > >
>> > > However, I suspect there's a build failure in Drools and looks like a
>> > > legitimate issue, this came up during the docs removal PR [1]. I'd
>> > > appreciate it if any Drools SME could double check before proceeding
>> > > with the release.
>> > >
>> > > [1] - https://github.com/apache/incubator-kie-drools/pull/6327
>> > >
>> > > On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <al...@porcelli.me>
>> wrote:
>> > > >
>> > > > Hi Team,
>> > > >
>> > > > Just a quick update - unfortunately, I discovered today that the
>> > > > branching pipelines for Kogito have failed, resulting in the 10.1.x
>> > > > branches being created with the 999-SNAPSHOT version in a few
>> > > > repositories (runtimes and apps)
>> > > >
>> > > > I attempted to re-run the pipeline, but unfortunately, that didn’t
>> > > > resolve the issue. At this point, I'm considering manually pushing
>> the
>> > > > version update. The alternative would be to ask Apache Infra to
>> delete
>> > > > the branches across all repositories so we can create a new weekly
>> > > > build, sync with KIE Tools, and restart the branching process from
>> > > > scratch.
>> > > >
>> > > > I’ll revisit this on Monday, as I have a planned day off tomorrow.
>> > > >
>> > > > -
>> > > > Alex
>> > > >
>> > > > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me>
>> wrote:
>> > > > >
>> > > > > Hi all,
>> > > > >
>> > > > > Just a quick update: all Jenkins release pipelines are currently
>> > > > > outdated and non-functional. During the 10.0.0 release, several
>> > > > > changes were made to the pipelines that were never fully brought
>> back
>> > > > > to main. Additionally, some modifications exist only on main and
>> were
>> > > > > not applied consistently across the different release branches.
>> > > > >
>> > > > > As a result, I'm currently working through each pipeline,
>> resolving a
>> > > > > number of conflicts and inconsistencies to bring them back into
>> sync.
>> > > > > This has proven to be quite time-consuming.
>> > > > >
>> > > > > Full transparency: I'm doing some direct commits/pushes for those
>> > > > > isolated CI-related changes to the 10.1.x branch. Much of this
>> work
>> > > > > involves trial and error due to the lack of a local Jenkins
>> > > > > environment that mirrors Apache's setup. Requiring PR reviews for
>> > > > > every small change would significantly slow down progress and
>> make an
>> > > > > already complex task even harder.
>> > > > >
>> > > > > I’ll keep you posted as things evolve.
>> > > > >
>> > > > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
>> > > > > <ri...@gmail.com> wrote:
>> > > > > >
>> > > > > > +1
>> > > > > >
>> > > > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <alex@porcelli.me
>> >
>> > > wrote:
>> > > > > >
>> > > > > > > Quick update, the release repositories have been branched.
>> > > > > > >
>> > > > > > > For more dynamic updates, we have a topic [1] in Zulip.
>> > > > > > >
>> > > > > > > [1] -
>> > > > > > >
>> > >
>> https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
>> > > > > > >
>> > > > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <
>> pibizza@gmail.com>
>> > > wrote:
>> > > > > > > >
>> > > > > > > > As said by others, happy to learn and help here.
>> > > > > > > >
>> > > > > > > > Regards
>> > > > > > > >
>> > > > > > > > P.
>> > > > > > > >
>> > > > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <
>> alex@porcelli.me>
>> > > wrote:
>> > > > > > > >
>> > > > > > > > > In light of recent discussions and the challenges we've
>> faced
>> > > as a
>> > > > > > > > > community, I propose a pragmatic step forward: a
>> short-term
>> > > 10.1.0
>> > > > > > > > > release cut directly from the main.
>> > > > > > > > >
>> > > > > > > > > While 10.0.0 was officially released in December, the
>> branch
>> > > for that
>> > > > > > > > > release was cut mid-last year, meaning that our current
>> > > codebase has
>> > > > > > > > > significantly evolved since then. Given the substantial
>> > > improvements
>> > > > > > > > > and fixes accumulated over the past months, I believe an
>> > > immediate
>> > > > > > > > > 10.1.0 release would provide tangible value to our user
>> base.
>> > > > > > > > >
>> > > > > > > > > This proposal puts our users first by ensuring they
>> receive an
>> > > updated
>> > > > > > > > > and more stable version without further delay.
>> > > > > > > > >
>> > > > > > > > > With this in mind, I propose the following:
>> > > > > > > > >
>> > > > > > > > > - Temporarily pausing the implementation of previously
>> voted
>> > > proposals
>> > > > > > > > > to allow time for a proper discussion on our bylaws and to
>> > > give the
>> > > > > > > > > community space to heal from recent escalations.
>> > > > > > > > > - Focusing on delivering 10.1.0 as an incremental update
>> that
>> > > brings
>> > > > > > > > > our latest work to users sooner rather than later.
>> > > > > > > > > - Cutting the release branch early next week, assuming
>> there is
>> > > > > > > consensus.
>> > > > > > > > >
>> > > > > > > > > I’m happy to take the lead in managing the release
>> process and
>> > > would
>> > > > > > > > > appreciate feedback on the proposal and the timing for
>> > > branching.
>> > > > > > > > >
>> > > > > > > > > I'm looking forward to hearing your thoughts.
>> > > > > > > > >
>> > > > > > > > > -
>> > > > > > > > > Alex
>> > > > > > > > >
>> > > > > > > > >
>> > > ---------------------------------------------------------------------
>> > > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
>> > > > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > ---------------------------------------------------------------------
>> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
>> > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
>> > > > > > >
>> > > > > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
>> > > For additional commands, e-mail: dev-help@kie.apache.org
>> > >
>> > >
>>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Quick update.
At this point I already have in staging all runtimes, however the release
pipelines in Jenkins for all KIE Tools are completely broken.
They need a complete througout review. Eduardo and Tiago volunteered to
help review. Given individuals agenda, we’ll meet to work on this next
Tuesday end of the day (eastern time)
Regards,
_____________
Alex Porcelli
http://porcelli.me
On Wed, Apr 30, 2025 at 10:24 AM Alex Porcelli <al...@porcelli.me> wrote:
> Thank you, Toshiya!
>
> Drools build started!
>
> On Wed, Apr 30, 2025 at 12:14 AM Toshiya Kobayashi
> <to...@gmail.com> wrote:
> >
> > Thank you, Alex.
> >
> > I'm looking at the drools test failure and filed a fix PR :
> > https://github.com/apache/incubator-kie-drools/pull/6328
> >
> > Toshiya
> >
> >
> > On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <al...@porcelli.me> wrote:
> >
> > > Since yesterday a new attempt to release is in progress.
> > >
> > > The good news: after fighting with pipelines, the 10.1.x branches are
> > > correctly created and with the proper version in place.
> > >
> > > However, I suspect there's a build failure in Drools and looks like a
> > > legitimate issue, this came up during the docs removal PR [1]. I'd
> > > appreciate it if any Drools SME could double check before proceeding
> > > with the release.
> > >
> > > [1] - https://github.com/apache/incubator-kie-drools/pull/6327
> > >
> > > On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <al...@porcelli.me>
> wrote:
> > > >
> > > > Hi Team,
> > > >
> > > > Just a quick update - unfortunately, I discovered today that the
> > > > branching pipelines for Kogito have failed, resulting in the 10.1.x
> > > > branches being created with the 999-SNAPSHOT version in a few
> > > > repositories (runtimes and apps)
> > > >
> > > > I attempted to re-run the pipeline, but unfortunately, that didn’t
> > > > resolve the issue. At this point, I'm considering manually pushing
> the
> > > > version update. The alternative would be to ask Apache Infra to
> delete
> > > > the branches across all repositories so we can create a new weekly
> > > > build, sync with KIE Tools, and restart the branching process from
> > > > scratch.
> > > >
> > > > I’ll revisit this on Monday, as I have a planned day off tomorrow.
> > > >
> > > > -
> > > > Alex
> > > >
> > > > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me>
> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Just a quick update: all Jenkins release pipelines are currently
> > > > > outdated and non-functional. During the 10.0.0 release, several
> > > > > changes were made to the pipelines that were never fully brought
> back
> > > > > to main. Additionally, some modifications exist only on main and
> were
> > > > > not applied consistently across the different release branches.
> > > > >
> > > > > As a result, I'm currently working through each pipeline,
> resolving a
> > > > > number of conflicts and inconsistencies to bring them back into
> sync.
> > > > > This has proven to be quite time-consuming.
> > > > >
> > > > > Full transparency: I'm doing some direct commits/pushes for those
> > > > > isolated CI-related changes to the 10.1.x branch. Much of this work
> > > > > involves trial and error due to the lack of a local Jenkins
> > > > > environment that mirrors Apache's setup. Requiring PR reviews for
> > > > > every small change would significantly slow down progress and make
> an
> > > > > already complex task even harder.
> > > > >
> > > > > I’ll keep you posted as things evolve.
> > > > >
> > > > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> > > > > <ri...@gmail.com> wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me>
> > > wrote:
> > > > > >
> > > > > > > Quick update, the release repositories have been branched.
> > > > > > >
> > > > > > > For more dynamic updates, we have a topic [1] in Zulip.
> > > > > > >
> > > > > > > [1] -
> > > > > > >
> > >
> https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> > > > > > >
> > > > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <
> pibizza@gmail.com>
> > > wrote:
> > > > > > > >
> > > > > > > > As said by others, happy to learn and help here.
> > > > > > > >
> > > > > > > > Regards
> > > > > > > >
> > > > > > > > P.
> > > > > > > >
> > > > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <
> alex@porcelli.me>
> > > wrote:
> > > > > > > >
> > > > > > > > > In light of recent discussions and the challenges we've
> faced
> > > as a
> > > > > > > > > community, I propose a pragmatic step forward: a short-term
> > > 10.1.0
> > > > > > > > > release cut directly from the main.
> > > > > > > > >
> > > > > > > > > While 10.0.0 was officially released in December, the
> branch
> > > for that
> > > > > > > > > release was cut mid-last year, meaning that our current
> > > codebase has
> > > > > > > > > significantly evolved since then. Given the substantial
> > > improvements
> > > > > > > > > and fixes accumulated over the past months, I believe an
> > > immediate
> > > > > > > > > 10.1.0 release would provide tangible value to our user
> base.
> > > > > > > > >
> > > > > > > > > This proposal puts our users first by ensuring they
> receive an
> > > updated
> > > > > > > > > and more stable version without further delay.
> > > > > > > > >
> > > > > > > > > With this in mind, I propose the following:
> > > > > > > > >
> > > > > > > > > - Temporarily pausing the implementation of previously
> voted
> > > proposals
> > > > > > > > > to allow time for a proper discussion on our bylaws and to
> > > give the
> > > > > > > > > community space to heal from recent escalations.
> > > > > > > > > - Focusing on delivering 10.1.0 as an incremental update
> that
> > > brings
> > > > > > > > > our latest work to users sooner rather than later.
> > > > > > > > > - Cutting the release branch early next week, assuming
> there is
> > > > > > > consensus.
> > > > > > > > >
> > > > > > > > > I’m happy to take the lead in managing the release process
> and
> > > would
> > > > > > > > > appreciate feedback on the proposal and the timing for
> > > branching.
> > > > > > > > >
> > > > > > > > > I'm looking forward to hearing your thoughts.
> > > > > > > > >
> > > > > > > > > -
> > > > > > > > > Alex
> > > > > > > > >
> > > > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > > >
> > > > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> > >
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Thank you, Toshiya!
Drools build started!
On Wed, Apr 30, 2025 at 12:14 AM Toshiya Kobayashi
<to...@gmail.com> wrote:
>
> Thank you, Alex.
>
> I'm looking at the drools test failure and filed a fix PR :
> https://github.com/apache/incubator-kie-drools/pull/6328
>
> Toshiya
>
>
> On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <al...@porcelli.me> wrote:
>
> > Since yesterday a new attempt to release is in progress.
> >
> > The good news: after fighting with pipelines, the 10.1.x branches are
> > correctly created and with the proper version in place.
> >
> > However, I suspect there's a build failure in Drools and looks like a
> > legitimate issue, this came up during the docs removal PR [1]. I'd
> > appreciate it if any Drools SME could double check before proceeding
> > with the release.
> >
> > [1] - https://github.com/apache/incubator-kie-drools/pull/6327
> >
> > On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <al...@porcelli.me> wrote:
> > >
> > > Hi Team,
> > >
> > > Just a quick update - unfortunately, I discovered today that the
> > > branching pipelines for Kogito have failed, resulting in the 10.1.x
> > > branches being created with the 999-SNAPSHOT version in a few
> > > repositories (runtimes and apps)
> > >
> > > I attempted to re-run the pipeline, but unfortunately, that didn’t
> > > resolve the issue. At this point, I'm considering manually pushing the
> > > version update. The alternative would be to ask Apache Infra to delete
> > > the branches across all repositories so we can create a new weekly
> > > build, sync with KIE Tools, and restart the branching process from
> > > scratch.
> > >
> > > I’ll revisit this on Monday, as I have a planned day off tomorrow.
> > >
> > > -
> > > Alex
> > >
> > > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Just a quick update: all Jenkins release pipelines are currently
> > > > outdated and non-functional. During the 10.0.0 release, several
> > > > changes were made to the pipelines that were never fully brought back
> > > > to main. Additionally, some modifications exist only on main and were
> > > > not applied consistently across the different release branches.
> > > >
> > > > As a result, I'm currently working through each pipeline, resolving a
> > > > number of conflicts and inconsistencies to bring them back into sync.
> > > > This has proven to be quite time-consuming.
> > > >
> > > > Full transparency: I'm doing some direct commits/pushes for those
> > > > isolated CI-related changes to the 10.1.x branch. Much of this work
> > > > involves trial and error due to the lack of a local Jenkins
> > > > environment that mirrors Apache's setup. Requiring PR reviews for
> > > > every small change would significantly slow down progress and make an
> > > > already complex task even harder.
> > > >
> > > > I’ll keep you posted as things evolve.
> > > >
> > > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> > > > <ri...@gmail.com> wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me>
> > wrote:
> > > > >
> > > > > > Quick update, the release repositories have been branched.
> > > > > >
> > > > > > For more dynamic updates, we have a topic [1] in Zulip.
> > > > > >
> > > > > > [1] -
> > > > > >
> > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> > > > > >
> > > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com>
> > wrote:
> > > > > > >
> > > > > > > As said by others, happy to learn and help here.
> > > > > > >
> > > > > > > Regards
> > > > > > >
> > > > > > > P.
> > > > > > >
> > > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me>
> > wrote:
> > > > > > >
> > > > > > > > In light of recent discussions and the challenges we've faced
> > as a
> > > > > > > > community, I propose a pragmatic step forward: a short-term
> > 10.1.0
> > > > > > > > release cut directly from the main.
> > > > > > > >
> > > > > > > > While 10.0.0 was officially released in December, the branch
> > for that
> > > > > > > > release was cut mid-last year, meaning that our current
> > codebase has
> > > > > > > > significantly evolved since then. Given the substantial
> > improvements
> > > > > > > > and fixes accumulated over the past months, I believe an
> > immediate
> > > > > > > > 10.1.0 release would provide tangible value to our user base.
> > > > > > > >
> > > > > > > > This proposal puts our users first by ensuring they receive an
> > updated
> > > > > > > > and more stable version without further delay.
> > > > > > > >
> > > > > > > > With this in mind, I propose the following:
> > > > > > > >
> > > > > > > > - Temporarily pausing the implementation of previously voted
> > proposals
> > > > > > > > to allow time for a proper discussion on our bylaws and to
> > give the
> > > > > > > > community space to heal from recent escalations.
> > > > > > > > - Focusing on delivering 10.1.0 as an incremental update that
> > brings
> > > > > > > > our latest work to users sooner rather than later.
> > > > > > > > - Cutting the release branch early next week, assuming there is
> > > > > > consensus.
> > > > > > > >
> > > > > > > > I’m happy to take the lead in managing the release process and
> > would
> > > > > > > > appreciate feedback on the proposal and the timing for
> > branching.
> > > > > > > >
> > > > > > > > I'm looking forward to hearing your thoughts.
> > > > > > > >
> > > > > > > > -
> > > > > > > > Alex
> > > > > > > >
> > > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > >
> > > > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Toshiya Kobayashi <to...@gmail.com>.
Thank you, Alex.
I'm looking at the drools test failure and filed a fix PR :
https://github.com/apache/incubator-kie-drools/pull/6328
Toshiya
On Wed, Apr 30, 2025 at 6:13 AM Alex Porcelli <al...@porcelli.me> wrote:
> Since yesterday a new attempt to release is in progress.
>
> The good news: after fighting with pipelines, the 10.1.x branches are
> correctly created and with the proper version in place.
>
> However, I suspect there's a build failure in Drools and looks like a
> legitimate issue, this came up during the docs removal PR [1]. I'd
> appreciate it if any Drools SME could double check before proceeding
> with the release.
>
> [1] - https://github.com/apache/incubator-kie-drools/pull/6327
>
> On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <al...@porcelli.me> wrote:
> >
> > Hi Team,
> >
> > Just a quick update - unfortunately, I discovered today that the
> > branching pipelines for Kogito have failed, resulting in the 10.1.x
> > branches being created with the 999-SNAPSHOT version in a few
> > repositories (runtimes and apps)
> >
> > I attempted to re-run the pipeline, but unfortunately, that didn’t
> > resolve the issue. At this point, I'm considering manually pushing the
> > version update. The alternative would be to ask Apache Infra to delete
> > the branches across all repositories so we can create a new weekly
> > build, sync with KIE Tools, and restart the branching process from
> > scratch.
> >
> > I’ll revisit this on Monday, as I have a planned day off tomorrow.
> >
> > -
> > Alex
> >
> > On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me> wrote:
> > >
> > > Hi all,
> > >
> > > Just a quick update: all Jenkins release pipelines are currently
> > > outdated and non-functional. During the 10.0.0 release, several
> > > changes were made to the pipelines that were never fully brought back
> > > to main. Additionally, some modifications exist only on main and were
> > > not applied consistently across the different release branches.
> > >
> > > As a result, I'm currently working through each pipeline, resolving a
> > > number of conflicts and inconsistencies to bring them back into sync.
> > > This has proven to be quite time-consuming.
> > >
> > > Full transparency: I'm doing some direct commits/pushes for those
> > > isolated CI-related changes to the 10.1.x branch. Much of this work
> > > involves trial and error due to the lack of a local Jenkins
> > > environment that mirrors Apache's setup. Requiring PR reviews for
> > > every small change would significantly slow down progress and make an
> > > already complex task even harder.
> > >
> > > I’ll keep you posted as things evolve.
> > >
> > > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> > > <ri...@gmail.com> wrote:
> > > >
> > > > +1
> > > >
> > > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me>
> wrote:
> > > >
> > > > > Quick update, the release repositories have been branched.
> > > > >
> > > > > For more dynamic updates, we have a topic [1] in Zulip.
> > > > >
> > > > > [1] -
> > > > >
> https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> > > > >
> > > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com>
> wrote:
> > > > > >
> > > > > > As said by others, happy to learn and help here.
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > P.
> > > > > >
> > > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me>
> wrote:
> > > > > >
> > > > > > > In light of recent discussions and the challenges we've faced
> as a
> > > > > > > community, I propose a pragmatic step forward: a short-term
> 10.1.0
> > > > > > > release cut directly from the main.
> > > > > > >
> > > > > > > While 10.0.0 was officially released in December, the branch
> for that
> > > > > > > release was cut mid-last year, meaning that our current
> codebase has
> > > > > > > significantly evolved since then. Given the substantial
> improvements
> > > > > > > and fixes accumulated over the past months, I believe an
> immediate
> > > > > > > 10.1.0 release would provide tangible value to our user base.
> > > > > > >
> > > > > > > This proposal puts our users first by ensuring they receive an
> updated
> > > > > > > and more stable version without further delay.
> > > > > > >
> > > > > > > With this in mind, I propose the following:
> > > > > > >
> > > > > > > - Temporarily pausing the implementation of previously voted
> proposals
> > > > > > > to allow time for a proper discussion on our bylaws and to
> give the
> > > > > > > community space to heal from recent escalations.
> > > > > > > - Focusing on delivering 10.1.0 as an incremental update that
> brings
> > > > > > > our latest work to users sooner rather than later.
> > > > > > > - Cutting the release branch early next week, assuming there is
> > > > > consensus.
> > > > > > >
> > > > > > > I’m happy to take the lead in managing the release process and
> would
> > > > > > > appreciate feedback on the proposal and the timing for
> branching.
> > > > > > >
> > > > > > > I'm looking forward to hearing your thoughts.
> > > > > > >
> > > > > > > -
> > > > > > > Alex
> > > > > > >
> > > > > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > >
> > > > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Since yesterday a new attempt to release is in progress.
The good news: after fighting with pipelines, the 10.1.x branches are
correctly created and with the proper version in place.
However, I suspect there's a build failure in Drools and looks like a
legitimate issue, this came up during the docs removal PR [1]. I'd
appreciate it if any Drools SME could double check before proceeding
with the release.
[1] - https://github.com/apache/incubator-kie-drools/pull/6327
On Thu, Mar 27, 2025 at 8:29 PM Alex Porcelli <al...@porcelli.me> wrote:
>
> Hi Team,
>
> Just a quick update - unfortunately, I discovered today that the
> branching pipelines for Kogito have failed, resulting in the 10.1.x
> branches being created with the 999-SNAPSHOT version in a few
> repositories (runtimes and apps)
>
> I attempted to re-run the pipeline, but unfortunately, that didn’t
> resolve the issue. At this point, I'm considering manually pushing the
> version update. The alternative would be to ask Apache Infra to delete
> the branches across all repositories so we can create a new weekly
> build, sync with KIE Tools, and restart the branching process from
> scratch.
>
> I’ll revisit this on Monday, as I have a planned day off tomorrow.
>
> -
> Alex
>
> On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me> wrote:
> >
> > Hi all,
> >
> > Just a quick update: all Jenkins release pipelines are currently
> > outdated and non-functional. During the 10.0.0 release, several
> > changes were made to the pipelines that were never fully brought back
> > to main. Additionally, some modifications exist only on main and were
> > not applied consistently across the different release branches.
> >
> > As a result, I'm currently working through each pipeline, resolving a
> > number of conflicts and inconsistencies to bring them back into sync.
> > This has proven to be quite time-consuming.
> >
> > Full transparency: I'm doing some direct commits/pushes for those
> > isolated CI-related changes to the 10.1.x branch. Much of this work
> > involves trial and error due to the lack of a local Jenkins
> > environment that mirrors Apache's setup. Requiring PR reviews for
> > every small change would significantly slow down progress and make an
> > already complex task even harder.
> >
> > I’ll keep you posted as things evolve.
> >
> > On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> > <ri...@gmail.com> wrote:
> > >
> > > +1
> > >
> > > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me> wrote:
> > >
> > > > Quick update, the release repositories have been branched.
> > > >
> > > > For more dynamic updates, we have a topic [1] in Zulip.
> > > >
> > > > [1] -
> > > > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> > > >
> > > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com> wrote:
> > > > >
> > > > > As said by others, happy to learn and help here.
> > > > >
> > > > > Regards
> > > > >
> > > > > P.
> > > > >
> > > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> > > > >
> > > > > > In light of recent discussions and the challenges we've faced as a
> > > > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > > > release cut directly from the main.
> > > > > >
> > > > > > While 10.0.0 was officially released in December, the branch for that
> > > > > > release was cut mid-last year, meaning that our current codebase has
> > > > > > significantly evolved since then. Given the substantial improvements
> > > > > > and fixes accumulated over the past months, I believe an immediate
> > > > > > 10.1.0 release would provide tangible value to our user base.
> > > > > >
> > > > > > This proposal puts our users first by ensuring they receive an updated
> > > > > > and more stable version without further delay.
> > > > > >
> > > > > > With this in mind, I propose the following:
> > > > > >
> > > > > > - Temporarily pausing the implementation of previously voted proposals
> > > > > > to allow time for a proper discussion on our bylaws and to give the
> > > > > > community space to heal from recent escalations.
> > > > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > > > our latest work to users sooner rather than later.
> > > > > > - Cutting the release branch early next week, assuming there is
> > > > consensus.
> > > > > >
> > > > > > I’m happy to take the lead in managing the release process and would
> > > > > > appreciate feedback on the proposal and the timing for branching.
> > > > > >
> > > > > > I'm looking forward to hearing your thoughts.
> > > > > >
> > > > > > -
> > > > > > Alex
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > > >
> > > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > >
> > > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Hi Team,
Just a quick update - unfortunately, I discovered today that the
branching pipelines for Kogito have failed, resulting in the 10.1.x
branches being created with the 999-SNAPSHOT version in a few
repositories (runtimes and apps)
I attempted to re-run the pipeline, but unfortunately, that didn’t
resolve the issue. At this point, I'm considering manually pushing the
version update. The alternative would be to ask Apache Infra to delete
the branches across all repositories so we can create a new weekly
build, sync with KIE Tools, and restart the branching process from
scratch.
I’ll revisit this on Monday, as I have a planned day off tomorrow.
-
Alex
On Wed, Mar 26, 2025 at 11:26 AM Alex Porcelli <al...@porcelli.me> wrote:
>
> Hi all,
>
> Just a quick update: all Jenkins release pipelines are currently
> outdated and non-functional. During the 10.0.0 release, several
> changes were made to the pipelines that were never fully brought back
> to main. Additionally, some modifications exist only on main and were
> not applied consistently across the different release branches.
>
> As a result, I'm currently working through each pipeline, resolving a
> number of conflicts and inconsistencies to bring them back into sync.
> This has proven to be quite time-consuming.
>
> Full transparency: I'm doing some direct commits/pushes for those
> isolated CI-related changes to the 10.1.x branch. Much of this work
> involves trial and error due to the lack of a local Jenkins
> environment that mirrors Apache's setup. Requiring PR reviews for
> every small change would significantly slow down progress and make an
> already complex task even harder.
>
> I’ll keep you posted as things evolve.
>
> On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
> <ri...@gmail.com> wrote:
> >
> > +1
> >
> > On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me> wrote:
> >
> > > Quick update, the release repositories have been branched.
> > >
> > > For more dynamic updates, we have a topic [1] in Zulip.
> > >
> > > [1] -
> > > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> > >
> > > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com> wrote:
> > > >
> > > > As said by others, happy to learn and help here.
> > > >
> > > > Regards
> > > >
> > > > P.
> > > >
> > > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> > > >
> > > > > In light of recent discussions and the challenges we've faced as a
> > > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > > release cut directly from the main.
> > > > >
> > > > > While 10.0.0 was officially released in December, the branch for that
> > > > > release was cut mid-last year, meaning that our current codebase has
> > > > > significantly evolved since then. Given the substantial improvements
> > > > > and fixes accumulated over the past months, I believe an immediate
> > > > > 10.1.0 release would provide tangible value to our user base.
> > > > >
> > > > > This proposal puts our users first by ensuring they receive an updated
> > > > > and more stable version without further delay.
> > > > >
> > > > > With this in mind, I propose the following:
> > > > >
> > > > > - Temporarily pausing the implementation of previously voted proposals
> > > > > to allow time for a proper discussion on our bylaws and to give the
> > > > > community space to heal from recent escalations.
> > > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > > our latest work to users sooner rather than later.
> > > > > - Cutting the release branch early next week, assuming there is
> > > consensus.
> > > > >
> > > > > I’m happy to take the lead in managing the release process and would
> > > > > appreciate feedback on the proposal and the timing for branching.
> > > > >
> > > > > I'm looking forward to hearing your thoughts.
> > > > >
> > > > > -
> > > > > Alex
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Hi all,
Just a quick update: all Jenkins release pipelines are currently
outdated and non-functional. During the 10.0.0 release, several
changes were made to the pipelines that were never fully brought back
to main. Additionally, some modifications exist only on main and were
not applied consistently across the different release branches.
As a result, I'm currently working through each pipeline, resolving a
number of conflicts and inconsistencies to bring them back into sync.
This has proven to be quite time-consuming.
Full transparency: I'm doing some direct commits/pushes for those
isolated CI-related changes to the 10.1.x branch. Much of this work
involves trial and error due to the lack of a local Jenkins
environment that mirrors Apache's setup. Requiring PR reviews for
every small change would significantly slow down progress and make an
already complex task even harder.
I’ll keep you posted as things evolve.
On Tue, Mar 25, 2025 at 11:38 AM ricardo zanini fernandes
<ri...@gmail.com> wrote:
>
> +1
>
> On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me> wrote:
>
> > Quick update, the release repositories have been branched.
> >
> > For more dynamic updates, we have a topic [1] in Zulip.
> >
> > [1] -
> > https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
> >
> > On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com> wrote:
> > >
> > > As said by others, happy to learn and help here.
> > >
> > > Regards
> > >
> > > P.
> > >
> > > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> > >
> > > > In light of recent discussions and the challenges we've faced as a
> > > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > > release cut directly from the main.
> > > >
> > > > While 10.0.0 was officially released in December, the branch for that
> > > > release was cut mid-last year, meaning that our current codebase has
> > > > significantly evolved since then. Given the substantial improvements
> > > > and fixes accumulated over the past months, I believe an immediate
> > > > 10.1.0 release would provide tangible value to our user base.
> > > >
> > > > This proposal puts our users first by ensuring they receive an updated
> > > > and more stable version without further delay.
> > > >
> > > > With this in mind, I propose the following:
> > > >
> > > > - Temporarily pausing the implementation of previously voted proposals
> > > > to allow time for a proper discussion on our bylaws and to give the
> > > > community space to heal from recent escalations.
> > > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > > our latest work to users sooner rather than later.
> > > > - Cutting the release branch early next week, assuming there is
> > consensus.
> > > >
> > > > I’m happy to take the lead in managing the release process and would
> > > > appreciate feedback on the proposal and the timing for branching.
> > > >
> > > > I'm looking forward to hearing your thoughts.
> > > >
> > > > -
> > > > Alex
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > > For additional commands, e-mail: dev-help@kie.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by ricardo zanini fernandes <ri...@gmail.com>.
+1
On Thu, Mar 20, 2025 at 8:52 AM Alex Porcelli <al...@porcelli.me> wrote:
> Quick update, the release repositories have been branched.
>
> For more dynamic updates, we have a topic [1] in Zulip.
>
> [1] -
> https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
>
> On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com> wrote:
> >
> > As said by others, happy to learn and help here.
> >
> > Regards
> >
> > P.
> >
> > On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> >
> > > In light of recent discussions and the challenges we've faced as a
> > > community, I propose a pragmatic step forward: a short-term 10.1.0
> > > release cut directly from the main.
> > >
> > > While 10.0.0 was officially released in December, the branch for that
> > > release was cut mid-last year, meaning that our current codebase has
> > > significantly evolved since then. Given the substantial improvements
> > > and fixes accumulated over the past months, I believe an immediate
> > > 10.1.0 release would provide tangible value to our user base.
> > >
> > > This proposal puts our users first by ensuring they receive an updated
> > > and more stable version without further delay.
> > >
> > > With this in mind, I propose the following:
> > >
> > > - Temporarily pausing the implementation of previously voted proposals
> > > to allow time for a proper discussion on our bylaws and to give the
> > > community space to heal from recent escalations.
> > > - Focusing on delivering 10.1.0 as an incremental update that brings
> > > our latest work to users sooner rather than later.
> > > - Cutting the release branch early next week, assuming there is
> consensus.
> > >
> > > I’m happy to take the lead in managing the release process and would
> > > appreciate feedback on the proposal and the timing for branching.
> > >
> > > I'm looking forward to hearing your thoughts.
> > >
> > > -
> > > Alex
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > > For additional commands, e-mail: dev-help@kie.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Alex Porcelli <al...@porcelli.me>.
Quick update, the release repositories have been branched.
For more dynamic updates, we have a topic [1] in Zulip.
[1] - https://kie.zulipchat.com/#narrow/channel/386449-kie-dev/topic/10.2E1.20release.20megathread
On Tue, Mar 18, 2025 at 3:53 AM Paolo Bizzarri <pi...@gmail.com> wrote:
>
> As said by others, happy to learn and help here.
>
> Regards
>
> P.
>
> On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
>
> > In light of recent discussions and the challenges we've faced as a
> > community, I propose a pragmatic step forward: a short-term 10.1.0
> > release cut directly from the main.
> >
> > While 10.0.0 was officially released in December, the branch for that
> > release was cut mid-last year, meaning that our current codebase has
> > significantly evolved since then. Given the substantial improvements
> > and fixes accumulated over the past months, I believe an immediate
> > 10.1.0 release would provide tangible value to our user base.
> >
> > This proposal puts our users first by ensuring they receive an updated
> > and more stable version without further delay.
> >
> > With this in mind, I propose the following:
> >
> > - Temporarily pausing the implementation of previously voted proposals
> > to allow time for a proper discussion on our bylaws and to give the
> > community space to heal from recent escalations.
> > - Focusing on delivering 10.1.0 as an incremental update that brings
> > our latest work to users sooner rather than later.
> > - Cutting the release branch early next week, assuming there is consensus.
> >
> > I’m happy to take the lead in managing the release process and would
> > appreciate feedback on the proposal and the timing for branching.
> >
> > I'm looking forward to hearing your thoughts.
> >
> > -
> > Alex
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> > For additional commands, e-mail: dev-help@kie.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org
Re: [PROPOSAL] Immediate 10.1.0 Release from main
Posted by Paolo Bizzarri <pi...@gmail.com>.
As said by others, happy to learn and help here.
Regards
P.
On Fri, Mar 14, 2025 at 2:07 PM Alex Porcelli <al...@porcelli.me> wrote:
> In light of recent discussions and the challenges we've faced as a
> community, I propose a pragmatic step forward: a short-term 10.1.0
> release cut directly from the main.
>
> While 10.0.0 was officially released in December, the branch for that
> release was cut mid-last year, meaning that our current codebase has
> significantly evolved since then. Given the substantial improvements
> and fixes accumulated over the past months, I believe an immediate
> 10.1.0 release would provide tangible value to our user base.
>
> This proposal puts our users first by ensuring they receive an updated
> and more stable version without further delay.
>
> With this in mind, I propose the following:
>
> - Temporarily pausing the implementation of previously voted proposals
> to allow time for a proper discussion on our bylaws and to give the
> community space to heal from recent escalations.
> - Focusing on delivering 10.1.0 as an incremental update that brings
> our latest work to users sooner rather than later.
> - Cutting the release branch early next week, assuming there is consensus.
>
> I’m happy to take the lead in managing the release process and would
> appreciate feedback on the proposal and the timing for branching.
>
> I'm looking forward to hearing your thoughts.
>
> -
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>