Hi Jialiang, Thanks for driving the spring6 upgrade to completion! Happy to see our dependency modernized.
It looks like the upgrade was done in a feature branch, and then cherry picked to the trunk branch. It may be a good idea to send out a notice for a big change beforehand though. BTW, I see that the three jiras are affecting 3.0.0. Do they actually affect 3.0.0 or 3.1.0? Because if they are regressions after spring6 upgrade, they should not affect 3.0.0. On Fri, Apr 11, 2025 at 6:47 PM Jialiang <jialiangca...@gmail.com> wrote: > Hello friends of the community, > > Thank you to all the contributors and administrators for your collective > efforts—Apache Ambari 3.0 has been released! 🎉 > > Next, we will begin planning the new version. > The Spring 6-related code has already been merged into the trunk, but > there are likely many bugs at the moment, such as numerous failing unit > tests. > Here are three issues that have already been identified: > - [AMBARI-26438](https://issues.apache.org/jira/browse/AMBARI-26438) > - [AMBARI-26437](https://issues.apache.org/jira/browse/AMBARI-26437) > - [AMBARI-26436](https://issues.apache.org/jira/browse/AMBARI-26436) > > If you're interested, feel free to help fix them! > > For the next release after 3.0, in addition to bug fixes, we have the > following plans: > 1. Spring 6 update > 2. Support for one-click Docker cluster deployment > > Let’s work together to make Ambari even better! 🚀 > > Best regards, > > Jialiang > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > For additional commands, e-mail: dev-h...@ambari.apache.org > >
