This thread was meant to be about the technical aspects of replacing the version numbers in the pom files as a means of bumping the release version. I guess I'll just give it a go and hope it works. We can discuss 1.0 on a separate thread. ________________________________ From: Maria Jose Esteve <[email protected]> Sent: Monday, September 30, 2024 11:39 PM To: [email protected] <[email protected]> Subject: RE: Next Release 0.9.12 ?
What list of "minimums" do we need to be able to release version 1.0? Hiedra -----Mensaje original----- De: Piotr Zarzycki <[email protected]> Enviado el: lunes, 30 de septiembre de 2024 21:25 Para: [email protected] Asunto: Re: Next Release 0.9.12 ? I would love to name Royale finally 1.0. I would opt to do that after this release. :) pon., 30 wrz 2024 o 20:52 Harbs <[email protected]> napisał(a): > Agreed. Unless we want to jump to version 1.0. > > > On Sep 30, 2024, at 7:14 PM, Josh Tynjala > > <[email protected]> > wrote: > > > > Yeah, I’d say go for it. > > > > -- > > Josh Tynjala > > Bowler Hat LLC <https://bowlerhat.dev> > > > > > > On Sun, Sep 29, 2024 at 2:10 PM Yishay Weiss > > <[email protected]> > wrote: > > > >> Hi All > >> > >> Because npm version is out of sync with Royale versions I think we > >> need the next release version to be 0.9.12. If that's the case then > >> I'm > thinking > >> of just replacing all occurrences of > >> <version>0.9.11-SNAPSHOT</version> > >> with <version>0.9.12-SNAPSHOT</version> and then doing a regular build. > Can > >> anybody see a reason why that would not work? > >> > >> Thanks > >> Yishay > >> > > -- Piotr Zarzycki
