All Spring updates are in separate branches and haven't been merged into trunk, so 3.0 won't include some of the Spring code.
> On Jan 23, 2025, at 12:50, Battula, Brahma Reddy <[email protected]> > wrote: > > Oh, some are already merged. Then 3.0 will be partial spring upgrade changes.? > if yes, by default these changes will not be enabled? > > From: Jialiang Cai <[email protected]> > Date: Tuesday, 21 January 2025 at 11:21 AM > To: [email protected] <[email protected]> > Subject: Re: Proposal for Ambari 3.0 Release and Community Feedback > > Some PRs related to the Spring update have already been submitted. The Spring > update could be released as a minor version following 3.0. What do you think? > >> On Jan 20, 2025, at 23:50, Battula, Brahma Reddy <[email protected]> >> wrote: >> >> Ok. >> >> After one major release, planning another might take more time since we need >> to GA the 3.0, which could require a couple of releases. Hence, I requested >> if you could accommodate. >> >> From: Viraj Jasani <[email protected]> >> Date: Sunday, 19 January 2025 at 1:51 PM >> To: [email protected] <[email protected]> >> Subject: Re: Proposal for Ambari 3.0 Release and Community Feedback >> >> Thank you Jialiang, this is indeed tons of efforts that can be finally >> released with 3.0. >> >> +1 for 3.0 and 3.1 release agendas! >> >> >> On Thu, Jan 16, 2025 at 1:13 AM Jialiang Cai <[email protected]> >> wrote: >> >>> Thanks for your attention. >>> >>> The Hadoop router is already included. Alluxio will soon have contributors >>> submitting code and will be released in version 3.0. Spring will be >>> released in version 3.1, as the relevant contributors are on holiday. The >>> related work will continue when they return from their holiday, with an >>> expected release in version 3.1. >>> >>> The 3.0 release involves extensive work, including the launch of the new >>> Ambari website, which encompasses packaging and cluster testing of numerous >>> big data components for CentOS 7, Rocky Linux 8, and Rocky Linux 9. It also >>> includes setting up CDN services with Ambari domain binding, distributing >>> big data and Ambari installation packages, and creating installation >>> tutorials. Due to contributor bandwidth limitations, the 3.0 release is >>> expected to be completed in February. >>> >>> >>>> On Jan 16, 2025, at 17:06, Battula, Brahma Reddy >>> <[email protected]> wrote: >>>> >>>> Thanks for stating on this. >>>> It looks good to me, HDFS Router is also added right. Alluxio? >>>> >>>> how about spring changes .? >>>> >>>> From: Jialiang Cai <[email protected]> >>>> Date: Wednesday, 15 January 2025 at 8:23 AM >>>> To: [email protected] <[email protected]> >>>> Subject: Proposal for Ambari 3.0 Release and Community Feedback >>>> >>>> Dear Community Members, >>>> >>>> I hope this message finds you well. It has been quite some time since >>> the revival of Ambari, and while we have made progress, we have yet to >>> provide our users with a truly convenient and up-to-date big data cluster >>> management solution. Currently, we have Ambari 2.7.x, which is based on the >>> now outdated and closed-source HDP (Hortonworks Data Platform). Finding a >>> usable HDP installation package has become increasingly difficult. >>>> >>>> In the meantime, our trunk branch has accumulated a significant number >>> of commits and new features, including: >>>> >>>> 1. **Python 2 to Python 3 Upgrade**: Transitioning from Python 2 to >>> Python 3 to ensure compatibility with modern systems. >>>> 2. **JDK 8 to JDK 17 Upgrade**: Upgrading the Java Development Kit to >>> version 17 for better performance and security. >>>> 3. **Introduction of Ruff**: Integrating Ruff for improved code quality >>> and linting. >>>> 4. **Bigtop Stack as Default**: Replacing HDP with Bigtop as the default >>> stack for better flexibility and community support. >>>> 5. **Support for Rocky 8 and 9**: Ensuring compatibility with the latest >>> versions of Rocky Linux. >>>> 6. **jQuery and Bootstrap Upgrades**: Modernizing the front-end >>> libraries for a better user experience. >>>> 7. **Other Java Dependency Upgrades**: Various updates to Java >>> dependencies to keep the project secure and efficient. >>>> >>>> Given these substantial updates, I believe it is time to deliver a >>> brand-new version of Ambari to our users. We are currently planning the >>> release of Ambari 3.0, which will include all the major updates mentioned >>> above, along with numerous smaller updates, bug fixes, and improvements. >>>> >>>> Additionally, we aim to provide: >>>> - A **new Ambari website** with updated documentation. >>>> - **User tutorials** to help new and existing users get started with >>> Ambari. >>>> - **Local debugging guides** to assist developers in troubleshooting and >>> contributing to the project. >>>> - **Downloadable packages** for Ambari and related big data components >>> to make installation and setup easier for users. >>>> >>>> We would love to hear your thoughts on this proposal. Your feedback is >>> invaluable as we move forward with this release. Please share your >>> opinions, suggestions, and any concerns you might have. >>>> >>>> Thank you for your continued support and contributions to the Ambari >>> community. >>>> >>>> Best regards, >>>> Jialiang >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
