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 <[email protected]> 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 < > [email protected]> wrote: > > > +1 to that > > > > El jue, 5 oct 2023, 18:55, Tibor Zimányi <[email protected]> > > 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 <[email protected]> > > > Sent: Thursday, October 5, 2023 6:50:50 PM > > > To: [email protected] <[email protected]> > > > 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. > > > > > >
