Hi Nicolas,

Although we didn't make a decision, mixed in with this thread -
https://lists.apache.org/thread/8pyhnjs65ss6btsl8r93w6z21pyksclt - is a
discussion about abandoning the 22.01 branch in favour of creating a new
branch from trunk.

The justification for creating a new branch was to capture a lot of the
Groovy refactoring work that had gone into trunk without duplicating a
similar level of effort to port those same changes to the 22.01 branch.

I believe we left the conversation - but once again, we did not make an
official statement or carry out any sort of vote - broadly in favour of
creating a new branch some time after the completion of the Groovy
refactoring work. I would now expect this to be a 24.01 branch created
early in the new year.

Thanks,

Dan.

On Tue, 12 Dec 2023 at 15:51, Nicolas Malin <[email protected]>
wrote:

> Hello Michael,
>
> If I understood well, you propose to rename the 22.01 on 24.0.1.01  to
> be more synchronize with it releasing time ? If is no worries with this
> but what the name for the branch to stabilization ?
>
> Cheers,
> Nicolas
>
> Le 08/12/2023 à 17:53, Michael Brohl a écrit :
> > Hi Nicolas,
> >
> > given the time gone by I am thinking about if we should do an early
> > 24.x release instead of 22.01. 22.01 sounds quite old with the year
> > 2024 just a few days ahead.
> >
> > But yes, it would be great to have a new stable release out soon.
> >
> > Best regards,
> >
> > Michael Brohl
> >
> > ecomify GmbH - www.ecomify.de
> >
> >
> > Am 08.12.23 um 16:10 schrieb Nicolas Malin:
> >> Hello all,
> >>
> >> I know that I go out from my cave :D, there was a lot of work on the
> >> OFBiz improvement quality this year on groovy and deployment process.
> >>
> >> I saw two issues [1][2] to solve before run a release process. Do you
> >> saw other element before try to release the 22.01.01 ?
> >>
> >> Cheers,
> >>
> >> Nicolas
> >>
> >> [1] https://issues.apache.org/jira/browse/OFBIZ-12726
> >> [2] https://issues.apache.org/jira/browse/OFBIZ-12868
>


-- 
Daniel Watford

Reply via email to