Nikita, thank you for raising this important question. +1 for making Ignite 2 the default version on the website.
+1 for preparing common wording for public communication, maybe starting with a draft on Confluence. +0 for the banner about the pause. Maybe we should just say that we don't have plans for the next Ignite 3 release at the moment. The Apache Board also left a comment on our previous report, asking us to clarify the situation and provide a status update. I think we should be clear and transparent, but avoid making it sound like we have already decided the future of Ignite 3. I hope this is just a temporary pause, and Ignite 3 development will continue in the future. чт, 8 окт. 2026 г. в 15:12, Anton Vinogradov <[email protected]>: > +1 > > On Wed, Oct 7, 2026 at 10:30 PM Максим Михайлович Давыдов < > [email protected]> wrote: > > > +1 (non-binding) > > > > ср, 7 окт. 2026 г. в 22:26, Nikolay Izhikov <[email protected]>: > > > > > +1 > > > > > > ср, 7 окт. 2026 г. в 21:22, Nikita Amelchev <[email protected]>: > > > > > > > > Igniters, > > > > > > > > I would like to discuss how we communicate the status of Apache > Ignite > > > > 3 to users and propose making Ignite 2 the default version on the > > > > website. > > > > > > > > Development of Ignite 3 has been inactive since April 23, 2026, the > > > > date of the last commit to apache/ignite-3. Ignite 2 remains actively > > > > developed: 2.18.0 was released in May and 2.19.0 is being planned > [1]. > > > > > > > > Users keep asking about the status, and the answers exist only in the > > > > mailing lists. In the last three months the community has replied > that > > > > the project is paused [2] and recommended Ignite 2.x for new projects > > > > [3]. A request to the PMC for a public statement [4] has not been > > > > answered yet. > > > > > > > > The website currently presents Ignite 3 as the primary version: "Get > > > > started" and /docs/latest lead to Ignite 3.1.0 marked "Latest", 3.1.0 > > > > is listed first on the download page, and the Ignite 3 documentation > > > > contains no note about the status. As a result, new users choose 3.x > > > > based on the website and later learn from the lists that 2.x is the > > > > recommended option. > > > > > > > > I propose the following changes. They do not deprecate Ignite 3: the > > > > status note is dated and can be removed as soon as development of > > > > Ignite 3 resumes. > > > > > > > > 1. Add a status banner to the Ignite 3 documentation and the download > > > page: > > > > > > > > Status (October 2026). Active development of Apache Ignite 3 is > > > > paused. Ignite 3.1.0 remains available, but no next release is > > > > scheduled and bug fixes are not guaranteed. For new projects and > > > > production deployments the community recommends Apache Ignite 2.x, > > > > which is actively developed and maintained. > > > > > > > > 2. Point "Get started" and /docs/latest to the Ignite 2 documentation > > > > and list the latest 2.x release first on the download page. The > Ignite > > > > 3 documentation remains available under /docs/ignite3. > > > > > > > > If there are no objections within 72 hours, I will treat this as lazy > > > > consensus, file a ticket and prepare a pull request to > > > > apache/ignite-website. > > > > > > > > [1] https://lists.apache.org/thread/7p3y7x390khfo39o6q57hcpfzpbfsfqb > > > > [2] https://lists.apache.org/thread/wy2yldgydpcldxmjw6bbntx93mt2lbrg > > > > [3] https://lists.apache.org/thread/02190to24181hnw44qqxo00plc51grb3 > > > > [4] https://lists.apache.org/thread/0hz3drko5cpoofosxy4g90q98qyl0xc2 > > > > > > > > -- > > > > Best wishes, > > > > Nikita Amelchev > > > > > >
