SOLVED Production Version Numbers

[rpvw]

With 64.0.11 going to release, I was expecting that 62.0.20 would go to Stable (and perhaps LTS) but it seems to have been overlooked.

My installed version is shown as being 62.0.20 but the rest of the Tiers look like:

LTS 62 Exp. 2018-03-31
STABLE 11.62.0.17
RELEASE 11.64.0.11
CURRENT 11.64.0.11
EDGE 11.64.0.11

Is this by design ? I wanted to keep the 62.0.20 for a few more days, but selecting Stable or LTS is treated as a downgrade. Had to resort to switching Daily Updates to Manual.

 

[cPanelMichael]

Hello @rpvw,

The "Stable" and "LTS" build tiers won't always offer the most recent build published to the "Release" tier, even after a new major version is published to the "Release" tier (E.g. 62 to 64). These tiers still follow the guidelines documented at:

Product Versions and the Release Process - cPanel Knowledge Base - cPanel Documentation
cPanel Long-Term Support - Documentation - cPanel Documentation

Temporarily switching to "Manual" updates in "WHM >> Update Preferences" was the correct method to stay on cPanel version 62.0.20. More information on the cPanel update configuration is available at:

The cPanel Update Configuration File - cpupdate.conf - Documentation - cPanel Documentation

Thank you.

 

[mtindor]

This is directed to the cPanel folks. I've experienced this the past two times i've set my machines from Release on a specific version to LTS (so from WHM 60 Release to LTS 60 and then later WHM 62 Release to LTS 62).

1. I have the cPanel updates occur automatically, nightly.

WHM 62 Release current version: 62.0.20
LTS 62 current version: 62.0.17

Now, I don't want my servers to even have to attempt to upgrade to 64. I want to put them on LTS 62. Since I'm currently on WHM 62 Release (which is 62.0.20), when I change to LTS 62 it is going to downgrade me to 62.0.17 (per layer2.cpanel.net LTS versions).

This was the case when I wanted to switch to LTS 60 after 62 was out, and now when I want to switch to LTS 62 after 64 is out.

I run RELEASE across the board, and in fact I think that is what is shown in the WHM interface as the "recommended" setting. But obviously if I switch from WHM 62 Release which is at 62.0.20, to LTS 62 which is at 62.0.17, it's going to downgrade me.

So now I have to set things to manual update so the server doesn't try and update to 64, because i don't want to set it to LTS 62 and have it downgrade to 62.0.17

Seems like there should be some better synchronicity there -- where the LTS version (62.0.17) should be the same as the latest 62 Release version (62.0.20).

Mike

 

[cPanelMichael]

Hello @mtindor,

I've moved your post into an existing thread on this topic.

In addition to the previous response, note that the general expectation is that servers configured to use the "Release" build tier will continue to use that tier and thus would update from cPanel 62 to cPanel 64. If you find that a server is more suited towards a specific tier (e.g. you want to stay on 62 for a while longer), you'd want configure the server to use the LTS or Stable tier.

That said, I do understand the desire to see the LTS or Stable tiers updated with the most recent build before a new major version is published. I've notified one of our Community Managers (@cPanelBenny) about this thread to ensure your feedback is considered.

Thank you.

 

[cPanelMichael]

Hello,

To update, the tentative plan is to have 62.0.21 published to the LTS/Stable tiers within the next 24 hours.

Thank you.

 

[mtindor]

THanks, Michael. I actually agree with what you've said, and had a discussion about this with a hosting buddy of mine who also just stays on Stable and never has any problems if/when he decides he needs to switch to LTS.

Mike

 

[cPanelMichael]

Hello,

The Stable and LTS tiers are now updated to cPanel version 62.0.21.

Thanks!

 

[mtindor]

Hello,

The Stable and LTS tiers are now updated to cPanel version 62.0.21.

Thanks!

And my servers are now on LTS 62 (62.0.21). Thanks!

Mike