On Sat, Oct 12, 2019 at 1:17 AM Steinar Bang <[email protected]> wrote:
>
> Just a small status report on the promised karaf feature PRs:
>
> I had something appearently working against the 2.10 branches but I
> didn't manage to the the PRs ready before the 2.10 train left the
> platform, so I had to rebase to 2.11.

This was partly my fault, too, since I really wanted to get 2.10
release out before end of September, so that Spring releases could use
it.
But compared to 2.10, I want 2.11 to be completed much faster, more
similar to 1.x minor release schedule: ideally release candidates by
end of 2019, minor release maybe in January 2020.

> The primary karaf maintainer has also expressed interest in QAing the
> changes, but will wait until after the 2.11 rebase to do so.

This sounds good.

> So the current plan, is:
>  1. rebase the fix branches of the jackson repos to the 2.11 branches of
>     the repos (this is where I'm currently at)
>  2. smoke test the karaf features (basicaly verify that the OSGi bundles
>     load in apache karaf)
>  3. submit the changes for QA with the karaf maintainer
>  4. apply the changes from that QA, with the necessary smoke testing
>  5. create the PRs and submit them, plan for submission
>     1. write a comment that I'm starting in the issue that started
>        this[1]
>     2. submit the PRs the order already in the issue
>     3. write a new comment in the first issue that PR submission is
>        complete
>
> References:
> [1] <https://github.com/FasterXML/jackson-databind/issues/2434>

Thank you for the update. I hope Jackson users who run Jackson on OSGi
containers can help with this effort.

-+ Tatu +-

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jackson-dev/CAL4a10i-K2pO%3D1GjW%2BY_fcOWzeTRG91JzR%2BFL8TdkBVfH3DsNw%40mail.gmail.com.

Reply via email to