Hi Puppet Enterprise team, raising a concern about PE lifecycle planning. The official support lifecycle page (puppet.com/products/puppet-enterprise/support-lifecycle) still says PE 2026.0 is "expected August 2026" and that PE 2025.y standard support ends "August 2026 (projected)". Both dates have passed, and the page hasn't been updated or explained. Customers plan upgrades against these commitments. When they slip without notice, we can't plan responsibly, especially with PE 2023.8 support ending February 27, 2027. Please keep this page current and authoritative, with firm GA and end-of-support dates and a last-updated date. For an enterprise product this is table stakes. I'd also urge you to reconsider the "Latest / Latest-1" model. Under it, every release is effectively short-term: at most about 12 months of full support, then 12 months of fixes only. That forces a major upgrade across the whole fleet roughly every year. Enterprises need long-lived, predictable support windows, which is exactly what LTS provided. Is there any chance an LTS track comes back?

Hey Vadym, thanks for the note! Just wanted to let you know we saw this and @Gavin Patton (who manages the support lifecycle on this) will get you an answer.

thanks

I too am a little frustrated with the Latest / Latest - 1. This came from out of nowhere.

Hey @vchepkov. The language used on that page is purposefully loose for the sort of situations we currently find ourselves where the 2026 release has been pushed to a later date. This is important because delivering quality releases is our highest priority. But you're right that this page is used by customers to help plan upgrades and the dates here are no longer accurate. We are currently targeting the end of September or early October for PE 2026 and then we will update the page with firm dates so that upgrades can be more precisely planned. In regards to the LTS track, we are always evaluating if changes are going to be needed and you make a great point around the need for some customers to have long-lived versions that they can rely on for longer periods of time. We have been working as a team on how best we can meet this need with the new N and N-1 model. We have already been looking at an extended support option available to allow teams to stay on an EOL version and continue to receive support, and we will be able to provide updates in the future as planning for that option progresses.