I'm cutting the release now...
My head on 2.19.x is this now:
commit 036ac2850d6acc2a5c5beb3be9e983f375f9f9a4 (upstream/2.19.x,
apache/2.19.x, 2.19.x)
Author: Clebert Suconic <clebertsuco...@apache.org>
Date: Mon Jan 24 10:33:42 2022 -0500
NO-JIRA Update on cherry-pick-report
(cherry picked from commit 3af6d0d58c21c400d053f7a310882bb3247cb7fa)
please don't commit anything on 2.19.x until you see the release
upgrade commits...
thanks
On Mon, Jan 24, 2022 at 12:15 PM Clebert Suconic
<clebert.suco...@gmail.com> wrote:
>
> I will be tagging 2.19.x as 2.19.1 in two days, on Jan-26th.
>
>
> This following report will show a list of commits between 2.19.0 and
> HEAD of main, and you will see an XREF for every commit that was
> already cherry-picked:
>
> https://activemq.apache.org/components/artemis/download/cherry-pick-report-2.19.1
>
>
> And this following report will show a list of commits on 2.19.x:
>
> https://activemq.apache.org/components/artemis/download/commit-report-2.19.1
>
>
>
>
> I tried to bring as many Bug fixes from main into 2.19.x as I could
> for this first release...
>
>
> Notice I don't plan to keep maintaining 2.19.x like that... future
> releases will only include critical fixes and possible CVEs...
>
>
> Please let me know if you would like another specific commit to be
> brought into 2.19.x ...
>
> Bug fixes not brought were probably not included because of conflicts
> or another case.
>
> If you need a specific commit that is not listed or not included on
> 2.19.x, I would appreciate a Pull request towards 2.19.x with the
> cherry-pick -x and any conflicts already solved...
>
>
>
>
> --
> Clebert Suconic
--
Clebert Suconic
