New Jackson head branches, 2.x, 3.x

[Tatu Saloranta]

Quick note: after the 2.19.0 release (that just went out), I completed
changes proposed in JSTEP-12
(https://github.com/FasterXML/jackson-future-ideas/wiki/JSTEP-12).

Basically: the branch formerly called "master" was renamed as "3.x"
(and currently is for 3.0.0-rc4-SNAPSHOT versions), and new "2.x"
branch was added for 2.20.0-SNAPSHOT.
From 3.x future branches 3.0, 3.1 etc will be created upon release of
new minor versions; similarly from 2.x we'll get 2.20, 2.21 and so on.

For now, the default branch for repos is set to 2.x. Some time after
the 3.0.0 release this will probably change to 3.x.

-+ Tatu +-

[宮田木織]

Could you please release `2.18.4`?
There are changes in `kotlin-module` targeted for `2.18.4`.

https://github.com/FasterXML/jackson-module-kotlin/blob/2.18/release-notes/CREDITS-2.x#L18-L22

Or should I fix the release notes?

2025年4月25日(金) 11:59 Tatu Saloranta <ta...@fasterxml.com>:

--
You received this message because you are subscribed to the Google Groups "jackson-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jackson-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAL4a10jfWzaxa55xC19-LYzgeYyCSicGDP90eQf9PUk_rn-pow%40mail.gmail.com.

[Joo Hyuk Kim]

Not sure if 2.18.4 is scheduled, yet.

But why would u modify release note?

2025년 4월 28일 (월) 오후 1:58, 宮田木織 <boran...@gmail.com>님이 작성:

To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAEyvuyE-M-VA0N29v%3D2wnfJhsn-epAGT--c0hnKzCv%2BfTa-LzA%40mail.gmail.com.

[宮田木織]

>  But why would u modify release note?

The reason is that there is a section that states “will be released in 2.18.4”.
If 2.18.4 is not released, then they were actually released in 2.19.0, so I think the release notes should be revised to avoid confusing users.

2025年4月28日(月) 20:17 Joo Hyuk Kim <bean...@gmail.com>:

To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CALS-ipy0BA-yLjt74v2b9sDQgJL8P5PmmSithyEbprRyrvU8pg%40mail.gmail.com.

[Joo Hyuk Kim]

If part of 2.18.4 release note, should probably mean that it will be release.
Can't just release as soon as someone needs the fix right away.

Could you try using latest 2.18 branch?

To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAEyvuyFsdUc-KPreyE797MJUH29oquqsUc%3D04c4PWv-D%2By84fQ%40mail.gmail.com.

[Tatu Saloranta]

On Mon, Apr 28, 2025 at 6:42 AM 宮田木織 <boran...@gmail.com> wrote:
>
> > But why would u modify release note?
>
> The reason is that there is a section that states “will be released in 2.18.4”.
> If 2.18.4 is not released, then they were actually released in 2.19.0, so I think the release notes should be revised to avoid confusing users.

It is tricky to figure out, but the rule I follow is that the fix is
listed under the "oldest" version it applies to.

It would be also confusing if 2.18.4 release notes did not indicate a
fix that is included in it.

Maybe in future it is necessary to just include reference dups for all
relevant versions.

-+ Tatu +-

> To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAEyvuyFsdUc-KPreyE797MJUH29oquqsUc%3D04c4PWv-D%2By84fQ%40mail.gmail.com.

[宮田木織]

Sorry for the delay in replying.
Am I correct in my understanding that 2.18.4 will not be released without some kind of backport, and that the release notes should not be modified?

2025年4月29日(火) 4:20 Tatu Saloranta <tsalo...@gmail.com>:

To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAGrxA24A%2BCDT-P8yX6YavUEQqFx8Yn0ZohZgG6NxEJrtq8DT3A%40mail.gmail.com.

[Tatu Saloranta]

On Thu, May 1, 2025 at 5:46 AM 宮田木織 <boran...@gmail.com> wrote:
>
> Sorry for the delay in replying.
> Am I correct in my understanding that 2.18.4 will not be released without some kind of backport, and that the release notes should not be modified?

Hmmm. I am not 100% sure I understand the question. But, so: the fix
went in 2.18 branch, from which 2.18.4 will eventually be released.
Since there are a few other fixes, I will probably do the release
relatively soon. Each full patch release takes about 3 hours so it is
not a trivial task.

If you want to figure out whether particular Kotlin fixes were
included in 2.19.0, you can add a question on a relevant issue (or PR)
-- assuming there is no mention yet.
Or have a look at Git history (git log) for the branch; you can see
release tags and compare those to PR merge commits.

I hope this helps.

-+ Tatu +-

ps. Going forward I will probably start duplicating fix-notes on
different branches' release notes. I have usually already added notes
on GH issues themselves, about releases fix is to be included in.

> To view this discussion visit https://groups.google.com/d/msgid/jackson-dev/CAEyvuyGL-EYHW0SuHSC9TusFaxjnUK2eV9SUMamad%2BOsKMe3Ag%40mail.gmail.com.