Would anyone have issues with changing the branch to just 'main' since we're unlikely to have to maintain multiple versions like Grails? Assuming no objections, I was going to start a vote thread.
On Mon, Jul 28, 2025 at 12:22 PM Gianluca Sartori <g.sart...@gmail.com> wrote: > > Okay, that makes sense, thank you for the clarification! > > > Gianluca Sartori > -- > https://dueuno.com > > > On Mon, 28 Jul 2025 at 15:02, James Daugherty > <jdaughe...@jdresources.net.invalid> wrote: > > > I suggested 0.0.1 with the idea that we wouldn't release milestone/rcs > > to the gradle plugin portal. So once Grails 7 is finalized, we'd > > release it as 1.0.0, but up until then, we can increment the patch > > version. > > > > On Mon, Jul 28, 2025 at 8:11 AM Gianluca Sartori <g.sart...@gmail.com> > > wrote: > > > > > > I would suggest a major release number, like 1.0.0, if the plugin > > > group/name have changed. > > > > > > 0.0.1 looks like an early release to me (I would prefer to see a 1.x > > > release in my projects, but I admit it’s a purely psychological thing :) > > > > > > > > > Gianluca Sartori > > > -- > > > https://dueuno.com > > > > > > > > > On Mon, 28 Jul 2025 at 14:01, James Daugherty > > > <jdaughe...@jdresources.net.invalid> wrote: > > > > > > > Hi Everyone, > > > > > > > > Now that the Grails Publish plugin is split from core, should we > > change the > > > > version #? We could reset it to 0.0.1 for its first release. > > > > > > > > -James > > > > > >
