cPanel 102 EOL

[sparek-3]

Getting messages that cPanel 102 will reach end of life soon. This isn't particularly shocking, I've been expecting it. But the shocking part is that I've seen no mention of this any where on this forum or any announcement any where else. There's also no mention of any particular time, just "soon."

layer1 still shows cPanel 102 as the LTS tier. I would kind of expect one of the other versions to run up to LTS before cPanel 102 reaches EOL - since that would define a clear path for what the next LTS tier is - which I assume is probably cPanel 110?

Just kind of seems that the cPanel 102 end of life upcp announcement is being made without a lot of other announcements to back it up.

 

[cPRex]

Hey there! In general, the previous LTS version gets dropped in June of the next year. 110 will be the next LTS tier for sure. We mention the LTS release dates in our docs here:

Product Versions and the Release Process | cPanel & WHM Documentation

This document explains the cPanel & WHM version system and release process.

docs.cpanel.net

so this is just expected behavior every June.

 

[sparek-3]

I might suggest having this information or tidbit at http://layer1.cpanel.net - at least that's where I go for version information.

I don't know specifically when you intend to put cPanel 110 at LTS, if I were suggesting things I'd probably tell you to put cPanel 110 at LTS on June 1st and leave cPanel 102 on LTS as well until June 30th, but add a tag about cPanel 102 approaching end of life on June 30th.

That way people that go to http://layer1.cpanel.net for version information (which... may just be me?) can see that cPanel 102 is approaching end of life and that cPanel 110 will be the new LTS and they have a month to make that transition. Or do it 2 or 3 months before June 1st if you want to give people more time to make the transition.

 

[cPRex]

I don't hate this idea. There is a link to that docs page a bit further down on the layer1 page, but it's not very obvious. I've made a case for the documentation team to see if they can add some more clarity directly to the layer1 page.