Planning on starting 2.14.0-rc1 release process tomorrow (in 12+ hours or so)

[Tatu Saloranta]

Ok, so I have finally gotten to the point where I feel confident I can
release the first "release candidate" (*) for Jackson 2.14.0. Stuff
included should be documented at:

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14

The idea with 2.14.0-rc1 is to give users, integrators a chance to
help us figure out possible compatibility/integration issues before
releasing actual 2.14.0.

But I thought I'll send a note to see if anyone has anything they'd
urgently want merged in -- while there will still be time to merge
fixes after 2.14.0-rc1 and before 2.14.0, perhaps there is something
that should go in 2.14.0 to get more testing. Given that I hope not to
have to release 2.14.0-rc2 (will do if I have to, but ideally not).

On timeline: my intent is to follow up with actual 2.14.0 within 3-4
weeks if all goes well.
But we'll see how things go.

-+ Tatu +-

(*) Unlike name implies this is not really something that is ever
likely to be released as-is, but is a commonly used term/prefix for
versioning so...

[Tatu Saloranta]

2.14.0-rc1 release process starting now.

Please note that it may take a bit longer than usual, during which
there is an incomplete set of versions published: this because we have
to start with `jackson-bom` which defines a consistent set of
2.14.0-rc1 components -- but there is no good way to provide
atomicity.

I will send a note when the release is complete.

-+ Tatu +-

[Tatu Saloranta]

2.14.0-rc1 release process now complete.

Release notes at:

https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14

At this point all the help in testing this pre-release candidate would
be appreciated so that the official
2.14.0 can be released maybe around mid-October in the best case scenario.

-+ Tatu +-

[Tatu Saloranta]

Ok, I did not announce it starting, but Jackson 2.14.0-rc2 was just released.

So far I don't think we have received many bug reports for rc1, but
did get at least one positive confirmation from ElasticSearch folks.
It would be good to get some more feedback regarding compatibility, or
lack thereof.

As to changes between RC1 and RC2: I should have kept a log but I
didn't. One notable area of changes, for what it is worth,
is that of `JsonPointer`: I rewrote internals (it's not a big class
but still) to:

1. Avoid StackOverflowError when compiling super deep (10k or above)
pointer expressions (see [core#818])
2. Use significantly less memory for deep expressions (create
representation used with `JsonPointer.toString()` lazily)

and although all the existing tests pass (plus I added slightly more)
I would not be entirely surprised if there were edge cases
causing issues -- I almost missed needed changes to
`JsonPointer.equals(...)` and `JsonPointer.hashCode()`.

Anyway, any and all testing at this point would be very helpful. My
current thinking on releasing 2.14.0 final is that it could be done
by the end of October, that is, in 2 or 3 weeks. This would be good to
help with recent CVEs, for which fix is in 2.14.

-+ Tatu +-