Interesting. Could you share a concrete example, please? On Tue, Dec 12, 2023 at 8:16 PM Ralph Goers <ralph.go...@dslextreme.com> wrote:
> Maybe you could add comments to the schema to define what the enumerations > are intended for and what effect they have on the release? > > Ralph > > > On Dec 12, 2023, at 10:13 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > > > Got it. I will land a log4j-changelog change accordingly, implement the > CI > > magic, and update the release instructions. > > > > On Tue, 12 Dec 2023 at 17:41, Piotr P. Karwasz <piotr.karw...@gmail.com> > > wrote: > > > >> Hi Volkan, > >> > >> On Tue, 12 Dec 2023 at 17:00, Volkan Yazıcı <vol...@yazi.ci> wrote: > >>> Piotr, could you give me a well-defined formula of your desired > >> versioning > >>> scheme concerning minor/patch bumps? > >> > >> I agree with what Ralph proposed. > >> > >> What I don't agree with is the current practice to set up the **next** > >> release version always to the next minor release (with an empty set of > >> changes). > >> I would set it to the next patch release and only transform it into a > >> minor release if we add an `added` or `changed` changelog entry. > >> As Ralph said, the CI could do it. > >> > >> Piotr > >> > >
