You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kie.apache.org by ricardo zanini fernandes <ri...@gmail.com> on 2023/10/05 16:50:50 UTC
[DISCUSS] Branching policies
Hi!
We need to create branches from the main for the following repositories:
- incubator-kie-kogito-runtimes
- incubator-kie-kogito-apps
- incubator-kie-kogito-examples
- incubator-kie-kogito-images
- incubator-kie-kogito-serverless-workflow
- incubator-kie-drools
It will be used midstream for our internal build/specific company needs.
What is the policy for branching? Do we have anything in mind or can I just
create those branches?
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
Re: [DISCUSS] Branching policies
Posted by Kris Verlaenen <kr...@gmail.com>.
We discussed this more and provided more explanation that this is a first
step to figure out how we can introduce maintenance branches in the
community. There are a lot of other concerns we have to discuss and figure
out to actually get to that goal, but we believe this is a first step in
that direction, enabling upstream work as much as possible. If anyone
still has concerns, more than happy to explain more, or please reply to
this email thread with your concerns. Under the assumption that concerns
were properly addressed, these branches will be created, but we can always
revisit this based on feedback.
Thx,
Kris
On Fri, Oct 6, 2023 at 1:34 PM Kris Verlaenen <kr...@gmail.com>
wrote:
> To clarify, this is not meant to contain any company-specific changes. We
> are indeed using midstream for this. But the idea is to have certain
> branches in our apache community that we would like to maintain for a
> longer period of time. We could cherry-pick important fixes to that. We
> could consider doing LTS community releases in the community from those as
> well in the future.
>
> The idea is that these branches would typically be based on a specific
> community release branch that we would like to maintain for a longer period
> of time, like 1.45.x. However, since we are having challenges with getting
> CI / release pipelines up and running, the suggestion we are asking about
> is to create these branches manually this once (something like 1.44.2.x)
> until we get community releases up and running again and can rely on the
> release branches created as part of that as a result.
>
> Thx,
> Kris
>
> On Thu, Oct 5, 2023 at 8:03 PM ricardo zanini fernandes <
> ricardozanini@gmail.com> wrote:
>
>> I believe this is a one-time-only thing since we don't have a release
>> upstream yet (or plans that I know about), thus no official upstream
>> branch. So having a branch at this point is just that, a branch.
>>
>> I totally understand the concerns, thou. I'm also in favor of not
>> branching
>> for any company needs.
>>
>> Cheers!
>> --
>> Ricardo Zanini Fernandes
>> Vida longa e próspera.
>>
>>
>> On Thu, Oct 5, 2023 at 2:58 PM Enrique Gonzalez Martinez <
>> elguardian@gmail.com> wrote:
>>
>> > I guess tibor meant that for community releases it is ok to have a
>> branch
>> > but for company releases it is not practical as cadence, things
>> included,
>> > etc... Might differ in needs and support.
>> >
>> >
>> >
>> > El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <
>> > ricardozanini@gmail.com>
>> > escribió:
>> >
>> > > Hi! Not sure if I was clear on my message, but the branch is not to
>> work
>> > on
>> > > it for specific needs. It's just to have a branch at a certain point
>> in
>> > > time.
>> > >
>> > > Cheers!
>> > > --
>> > > Ricardo Zanini Fernandes
>> > > Vida longa e próspera.
>> > >
>> > >
>> > > On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
>> > > elguardian@gmail.com> wrote:
>> > >
>> > > > +1 to that
>> > > >
>> > > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
>> > > > escribió:
>> > > >
>> > > > > Hi Ricardo,
>> > > > >
>> > > > > for specific company needs I would recommend to have such
>> branches in
>> > > the
>> > > > > company mirrors. Apache is a community effort, so the focus is on
>> > > > community
>> > > > > release streams.
>> > > > >
>> > > > > Best regards,
>> > > > > Tibor
>> > > > >
>> > > > > ________________________________
>> > > > > From: ricardo zanini fernandes <ri...@gmail.com>
>> > > > > Sent: Thursday, October 5, 2023 6:50:50 PM
>> > > > > To: dev@kie.apache.org <de...@kie.apache.org>
>> > > > > Subject: [DISCUSS] Branching policies
>> > > > >
>> > > > > Hi!
>> > > > >
>> > > > > We need to create branches from the main for the following
>> > > repositories:
>> > > > >
>> > > > > - incubator-kie-kogito-runtimes
>> > > > > - incubator-kie-kogito-apps
>> > > > > - incubator-kie-kogito-examples
>> > > > > - incubator-kie-kogito-images
>> > > > > - incubator-kie-kogito-serverless-workflow
>> > > > > - incubator-kie-drools
>> > > > >
>> > > > > It will be used midstream for our internal build/specific company
>> > > needs.
>> > > > >
>> > > > > What is the policy for branching? Do we have anything in mind or
>> can
>> > I
>> > > > just
>> > > > > create those branches?
>> > > > >
>> > > > > Cheers!
>> > > > > --
>> > > > > Ricardo Zanini Fernandes
>> > > > > Vida longa e próspera.
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: [DISCUSS] Branching policies
Posted by Kris Verlaenen <kr...@gmail.com>.
To clarify, this is not meant to contain any company-specific changes. We
are indeed using midstream for this. But the idea is to have certain
branches in our apache community that we would like to maintain for a
longer period of time. We could cherry-pick important fixes to that. We
could consider doing LTS community releases in the community from those as
well in the future.
The idea is that these branches would typically be based on a specific
community release branch that we would like to maintain for a longer period
of time, like 1.45.x. However, since we are having challenges with getting
CI / release pipelines up and running, the suggestion we are asking about
is to create these branches manually this once (something like 1.44.2.x)
until we get community releases up and running again and can rely on the
release branches created as part of that as a result.
Thx,
Kris
On Thu, Oct 5, 2023 at 8:03 PM ricardo zanini fernandes <
ricardozanini@gmail.com> wrote:
> I believe this is a one-time-only thing since we don't have a release
> upstream yet (or plans that I know about), thus no official upstream
> branch. So having a branch at this point is just that, a branch.
>
> I totally understand the concerns, thou. I'm also in favor of not branching
> for any company needs.
>
> Cheers!
> --
> Ricardo Zanini Fernandes
> Vida longa e próspera.
>
>
> On Thu, Oct 5, 2023 at 2:58 PM Enrique Gonzalez Martinez <
> elguardian@gmail.com> wrote:
>
> > I guess tibor meant that for community releases it is ok to have a branch
> > but for company releases it is not practical as cadence, things included,
> > etc... Might differ in needs and support.
> >
> >
> >
> > El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <
> > ricardozanini@gmail.com>
> > escribió:
> >
> > > Hi! Not sure if I was clear on my message, but the branch is not to
> work
> > on
> > > it for specific needs. It's just to have a branch at a certain point in
> > > time.
> > >
> > > Cheers!
> > > --
> > > Ricardo Zanini Fernandes
> > > Vida longa e próspera.
> > >
> > >
> > > On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
> > > elguardian@gmail.com> wrote:
> > >
> > > > +1 to that
> > > >
> > > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> > > > escribió:
> > > >
> > > > > Hi Ricardo,
> > > > >
> > > > > for specific company needs I would recommend to have such branches
> in
> > > the
> > > > > company mirrors. Apache is a community effort, so the focus is on
> > > > community
> > > > > release streams.
> > > > >
> > > > > Best regards,
> > > > > Tibor
> > > > >
> > > > > ________________________________
> > > > > From: ricardo zanini fernandes <ri...@gmail.com>
> > > > > Sent: Thursday, October 5, 2023 6:50:50 PM
> > > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > > Subject: [DISCUSS] Branching policies
> > > > >
> > > > > Hi!
> > > > >
> > > > > We need to create branches from the main for the following
> > > repositories:
> > > > >
> > > > > - incubator-kie-kogito-runtimes
> > > > > - incubator-kie-kogito-apps
> > > > > - incubator-kie-kogito-examples
> > > > > - incubator-kie-kogito-images
> > > > > - incubator-kie-kogito-serverless-workflow
> > > > > - incubator-kie-drools
> > > > >
> > > > > It will be used midstream for our internal build/specific company
> > > needs.
> > > > >
> > > > > What is the policy for branching? Do we have anything in mind or
> can
> > I
> > > > just
> > > > > create those branches?
> > > > >
> > > > > Cheers!
> > > > > --
> > > > > Ricardo Zanini Fernandes
> > > > > Vida longa e próspera.
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Branching policies
Posted by ricardo zanini fernandes <ri...@gmail.com>.
That's fair enough! Thanks for sharing, Tibor.
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Thu, Oct 5, 2023 at 3:25 PM Tibor Zimányi <ti...@gmail.com>
wrote:
> I think Red Hat has the mirrors in kiegroup still available. I personally
> think, even if we are in a transition period in Incubator, we should be
> strict about the repositories, as the code is owned by Apache. What do
> others think please?
>
> Best regards,
> Tibor
>
> ________________________________
> From: ricardo zanini fernandes <ri...@gmail.com>
> Sent: Thursday, October 5, 2023 8:01:39 PM
> To: dev@kie.apache.org <de...@kie.apache.org>
> Subject: Re: [DISCUSS] Branching policies
>
> I believe this is a one-time-only thing since we don't have a release
> upstream yet (or plans that I know about), thus no official upstream
> branch. So having a branch at this point is just that, a branch.
>
> I totally understand the concerns, thou. I'm also in favor of not branching
> for any company needs.
>
> Cheers!
> --
> Ricardo Zanini Fernandes
> Vida longa e próspera.
>
>
> On Thu, Oct 5, 2023 at 2:58 PM Enrique Gonzalez Martinez <
> elguardian@gmail.com> wrote:
>
> > I guess tibor meant that for community releases it is ok to have a branch
> > but for company releases it is not practical as cadence, things included,
> > etc... Might differ in needs and support.
> >
> >
> >
> > El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <
> > ricardozanini@gmail.com>
> > escribió:
> >
> > > Hi! Not sure if I was clear on my message, but the branch is not to
> work
> > on
> > > it for specific needs. It's just to have a branch at a certain point in
> > > time.
> > >
> > > Cheers!
> > > --
> > > Ricardo Zanini Fernandes
> > > Vida longa e próspera.
> > >
> > >
> > > On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
> > > elguardian@gmail.com> wrote:
> > >
> > > > +1 to that
> > > >
> > > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> > > > escribió:
> > > >
> > > > > Hi Ricardo,
> > > > >
> > > > > for specific company needs I would recommend to have such branches
> in
> > > the
> > > > > company mirrors. Apache is a community effort, so the focus is on
> > > > community
> > > > > release streams.
> > > > >
> > > > > Best regards,
> > > > > Tibor
> > > > >
> > > > > ________________________________
> > > > > From: ricardo zanini fernandes <ri...@gmail.com>
> > > > > Sent: Thursday, October 5, 2023 6:50:50 PM
> > > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > > Subject: [DISCUSS] Branching policies
> > > > >
> > > > > Hi!
> > > > >
> > > > > We need to create branches from the main for the following
> > > repositories:
> > > > >
> > > > > - incubator-kie-kogito-runtimes
> > > > > - incubator-kie-kogito-apps
> > > > > - incubator-kie-kogito-examples
> > > > > - incubator-kie-kogito-images
> > > > > - incubator-kie-kogito-serverless-workflow
> > > > > - incubator-kie-drools
> > > > >
> > > > > It will be used midstream for our internal build/specific company
> > > needs.
> > > > >
> > > > > What is the policy for branching? Do we have anything in mind or
> can
> > I
> > > > just
> > > > > create those branches?
> > > > >
> > > > > Cheers!
> > > > > --
> > > > > Ricardo Zanini Fernandes
> > > > > Vida longa e próspera.
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Branching policies
Posted by Tibor Zimányi <ti...@gmail.com>.
I think Red Hat has the mirrors in kiegroup still available. I personally think, even if we are in a transition period in Incubator, we should be strict about the repositories, as the code is owned by Apache. What do others think please?
Best regards,
Tibor
________________________________
From: ricardo zanini fernandes <ri...@gmail.com>
Sent: Thursday, October 5, 2023 8:01:39 PM
To: dev@kie.apache.org <de...@kie.apache.org>
Subject: Re: [DISCUSS] Branching policies
I believe this is a one-time-only thing since we don't have a release
upstream yet (or plans that I know about), thus no official upstream
branch. So having a branch at this point is just that, a branch.
I totally understand the concerns, thou. I'm also in favor of not branching
for any company needs.
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Thu, Oct 5, 2023 at 2:58 PM Enrique Gonzalez Martinez <
elguardian@gmail.com> wrote:
> I guess tibor meant that for community releases it is ok to have a branch
> but for company releases it is not practical as cadence, things included,
> etc... Might differ in needs and support.
>
>
>
> El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <
> ricardozanini@gmail.com>
> escribió:
>
> > Hi! Not sure if I was clear on my message, but the branch is not to work
> on
> > it for specific needs. It's just to have a branch at a certain point in
> > time.
> >
> > Cheers!
> > --
> > Ricardo Zanini Fernandes
> > Vida longa e próspera.
> >
> >
> > On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
> > elguardian@gmail.com> wrote:
> >
> > > +1 to that
> > >
> > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> > > escribió:
> > >
> > > > Hi Ricardo,
> > > >
> > > > for specific company needs I would recommend to have such branches in
> > the
> > > > company mirrors. Apache is a community effort, so the focus is on
> > > community
> > > > release streams.
> > > >
> > > > Best regards,
> > > > Tibor
> > > >
> > > > ________________________________
> > > > From: ricardo zanini fernandes <ri...@gmail.com>
> > > > Sent: Thursday, October 5, 2023 6:50:50 PM
> > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > Subject: [DISCUSS] Branching policies
> > > >
> > > > Hi!
> > > >
> > > > We need to create branches from the main for the following
> > repositories:
> > > >
> > > > - incubator-kie-kogito-runtimes
> > > > - incubator-kie-kogito-apps
> > > > - incubator-kie-kogito-examples
> > > > - incubator-kie-kogito-images
> > > > - incubator-kie-kogito-serverless-workflow
> > > > - incubator-kie-drools
> > > >
> > > > It will be used midstream for our internal build/specific company
> > needs.
> > > >
> > > > What is the policy for branching? Do we have anything in mind or can
> I
> > > just
> > > > create those branches?
> > > >
> > > > Cheers!
> > > > --
> > > > Ricardo Zanini Fernandes
> > > > Vida longa e próspera.
> > > >
> > >
> >
>
Re: [DISCUSS] Branching policies
Posted by ricardo zanini fernandes <ri...@gmail.com>.
I believe this is a one-time-only thing since we don't have a release
upstream yet (or plans that I know about), thus no official upstream
branch. So having a branch at this point is just that, a branch.
I totally understand the concerns, thou. I'm also in favor of not branching
for any company needs.
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Thu, Oct 5, 2023 at 2:58 PM Enrique Gonzalez Martinez <
elguardian@gmail.com> wrote:
> I guess tibor meant that for community releases it is ok to have a branch
> but for company releases it is not practical as cadence, things included,
> etc... Might differ in needs and support.
>
>
>
> El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <
> ricardozanini@gmail.com>
> escribió:
>
> > Hi! Not sure if I was clear on my message, but the branch is not to work
> on
> > it for specific needs. It's just to have a branch at a certain point in
> > time.
> >
> > Cheers!
> > --
> > Ricardo Zanini Fernandes
> > Vida longa e próspera.
> >
> >
> > On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
> > elguardian@gmail.com> wrote:
> >
> > > +1 to that
> > >
> > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> > > escribió:
> > >
> > > > Hi Ricardo,
> > > >
> > > > for specific company needs I would recommend to have such branches in
> > the
> > > > company mirrors. Apache is a community effort, so the focus is on
> > > community
> > > > release streams.
> > > >
> > > > Best regards,
> > > > Tibor
> > > >
> > > > ________________________________
> > > > From: ricardo zanini fernandes <ri...@gmail.com>
> > > > Sent: Thursday, October 5, 2023 6:50:50 PM
> > > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > > Subject: [DISCUSS] Branching policies
> > > >
> > > > Hi!
> > > >
> > > > We need to create branches from the main for the following
> > repositories:
> > > >
> > > > - incubator-kie-kogito-runtimes
> > > > - incubator-kie-kogito-apps
> > > > - incubator-kie-kogito-examples
> > > > - incubator-kie-kogito-images
> > > > - incubator-kie-kogito-serverless-workflow
> > > > - incubator-kie-drools
> > > >
> > > > It will be used midstream for our internal build/specific company
> > needs.
> > > >
> > > > What is the policy for branching? Do we have anything in mind or can
> I
> > > just
> > > > create those branches?
> > > >
> > > > Cheers!
> > > > --
> > > > Ricardo Zanini Fernandes
> > > > Vida longa e próspera.
> > > >
> > >
> >
>
Re: [DISCUSS] Branching policies
Posted by Enrique Gonzalez Martinez <el...@gmail.com>.
I guess tibor meant that for community releases it is ok to have a branch
but for company releases it is not practical as cadence, things included,
etc... Might differ in needs and support.
El jue, 5 oct 2023, 19:48, ricardo zanini fernandes <ri...@gmail.com>
escribió:
> Hi! Not sure if I was clear on my message, but the branch is not to work on
> it for specific needs. It's just to have a branch at a certain point in
> time.
>
> Cheers!
> --
> Ricardo Zanini Fernandes
> Vida longa e próspera.
>
>
> On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
> elguardian@gmail.com> wrote:
>
> > +1 to that
> >
> > El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> > escribió:
> >
> > > Hi Ricardo,
> > >
> > > for specific company needs I would recommend to have such branches in
> the
> > > company mirrors. Apache is a community effort, so the focus is on
> > community
> > > release streams.
> > >
> > > Best regards,
> > > Tibor
> > >
> > > ________________________________
> > > From: ricardo zanini fernandes <ri...@gmail.com>
> > > Sent: Thursday, October 5, 2023 6:50:50 PM
> > > To: dev@kie.apache.org <de...@kie.apache.org>
> > > Subject: [DISCUSS] Branching policies
> > >
> > > Hi!
> > >
> > > We need to create branches from the main for the following
> repositories:
> > >
> > > - incubator-kie-kogito-runtimes
> > > - incubator-kie-kogito-apps
> > > - incubator-kie-kogito-examples
> > > - incubator-kie-kogito-images
> > > - incubator-kie-kogito-serverless-workflow
> > > - incubator-kie-drools
> > >
> > > It will be used midstream for our internal build/specific company
> needs.
> > >
> > > What is the policy for branching? Do we have anything in mind or can I
> > just
> > > create those branches?
> > >
> > > Cheers!
> > > --
> > > Ricardo Zanini Fernandes
> > > Vida longa e próspera.
> > >
> >
>
Re: [DISCUSS] Branching policies
Posted by ricardo zanini fernandes <ri...@gmail.com>.
Hi! Not sure if I was clear on my message, but the branch is not to work on
it for specific needs. It's just to have a branch at a certain point in
time.
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.
On Thu, Oct 5, 2023 at 1:56 PM Enrique Gonzalez Martinez <
elguardian@gmail.com> wrote:
> +1 to that
>
> El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com>
> escribió:
>
> > Hi Ricardo,
> >
> > for specific company needs I would recommend to have such branches in the
> > company mirrors. Apache is a community effort, so the focus is on
> community
> > release streams.
> >
> > Best regards,
> > Tibor
> >
> > ________________________________
> > From: ricardo zanini fernandes <ri...@gmail.com>
> > Sent: Thursday, October 5, 2023 6:50:50 PM
> > To: dev@kie.apache.org <de...@kie.apache.org>
> > Subject: [DISCUSS] Branching policies
> >
> > Hi!
> >
> > We need to create branches from the main for the following repositories:
> >
> > - incubator-kie-kogito-runtimes
> > - incubator-kie-kogito-apps
> > - incubator-kie-kogito-examples
> > - incubator-kie-kogito-images
> > - incubator-kie-kogito-serverless-workflow
> > - incubator-kie-drools
> >
> > It will be used midstream for our internal build/specific company needs.
> >
> > What is the policy for branching? Do we have anything in mind or can I
> just
> > create those branches?
> >
> > Cheers!
> > --
> > Ricardo Zanini Fernandes
> > Vida longa e próspera.
> >
>
Re: [DISCUSS] Branching policies
Posted by Enrique Gonzalez Martinez <el...@gmail.com>.
+1 to that
El jue, 5 oct 2023, 18:55, Tibor Zimányi <ti...@gmail.com> escribió:
> Hi Ricardo,
>
> for specific company needs I would recommend to have such branches in the
> company mirrors. Apache is a community effort, so the focus is on community
> release streams.
>
> Best regards,
> Tibor
>
> ________________________________
> From: ricardo zanini fernandes <ri...@gmail.com>
> Sent: Thursday, October 5, 2023 6:50:50 PM
> To: dev@kie.apache.org <de...@kie.apache.org>
> Subject: [DISCUSS] Branching policies
>
> Hi!
>
> We need to create branches from the main for the following repositories:
>
> - incubator-kie-kogito-runtimes
> - incubator-kie-kogito-apps
> - incubator-kie-kogito-examples
> - incubator-kie-kogito-images
> - incubator-kie-kogito-serverless-workflow
> - incubator-kie-drools
>
> It will be used midstream for our internal build/specific company needs.
>
> What is the policy for branching? Do we have anything in mind or can I just
> create those branches?
>
> Cheers!
> --
> Ricardo Zanini Fernandes
> Vida longa e próspera.
>
Re: [DISCUSS] Branching policies
Posted by Tibor Zimányi <ti...@gmail.com>.
Hi Ricardo,
for specific company needs I would recommend to have such branches in the company mirrors. Apache is a community effort, so the focus is on community release streams.
Best regards,
Tibor
________________________________
From: ricardo zanini fernandes <ri...@gmail.com>
Sent: Thursday, October 5, 2023 6:50:50 PM
To: dev@kie.apache.org <de...@kie.apache.org>
Subject: [DISCUSS] Branching policies
Hi!
We need to create branches from the main for the following repositories:
- incubator-kie-kogito-runtimes
- incubator-kie-kogito-apps
- incubator-kie-kogito-examples
- incubator-kie-kogito-images
- incubator-kie-kogito-serverless-workflow
- incubator-kie-drools
It will be used midstream for our internal build/specific company needs.
What is the policy for branching? Do we have anything in mind or can I just
create those branches?
Cheers!
--
Ricardo Zanini Fernandes
Vida longa e próspera.