In my opinion only the most critical fixes involving security or stability should be back-ported.
That said, I think we'd need more than just a single user here to warrant the effort to back-port and perform releases. Of course, in an ideal world the folks who actually need the fixes & releases would share the work-load. That would make this whole endeavor more viable. Lastly, it's worth mentioning that anybody can maintain their own branch and perform their own releases using 2.19.0 as a base. If the demand isn't high enough to warrant general releases I expect this is what we'd recommend. Justin On Wed, Dec 22, 2021 at 11:04 AM Clebert Suconic <[email protected]> wrote: > I wonder what should qualify for the cherry picking. > > One thing I must ask. To always use cherry pick -x > > I have a report tooling that would help to XREF the branches. > > On Wed, Dec 22, 2021 at 10:00 AM Viktor Kolomeyko > <[email protected]> wrote: > > > Hello, > > I would like to cast my vote supporting 2.19.x branch for JDK 1.8 users. > > We do have a version of our product which is still running on JRE 1.8 and > > we do need some critical fixes to be applied. > > In particular, I would want to see > > https://issues.apache.org/jira/browse/ARTEMIS-3593 to be included into > > 2.19.1 > > Many thanks, > > Viktor Kolomeyko > > > > On 2021/12/15 17:27:26 Clebert Suconic wrote: > > > I just sent ActiveMQ Artemis 2.20.0 to be reviewed under Vote. and I > > > would like to clarify that JDK 1.8 will not be supported any more from > > > Artemis 2.20.0 > > > > > > > > > At this point I don't think we need to create a 2.19.x branch for JDK > > > 1.8 Users. > > > > > > I would like to hear from anyone who can't move to JDK 11 here ... > > > > > > Here is a space for your complaints if you can't move, and I space > > > for us to convince you to move out of JDK 8 :) > > > > > > I had a few conversations with many other teams and I don't foresee a > > > reason to.. so, let me know if I'm wrong here. > > > -- > > > Clebert Suconic > > > > > > > R3 is committed to ensuring the security and protection of the personal > > data that we process, and to provide a compliant and consistent approach > to > > data protection. Any personal data that is shared as part of any email > > correspondence with R3 shall be processed in line with the R3 Privacy > > Policy<https://www.r3.com/full-privacy-policy/> > > > -- > Clebert Suconic >
