Why are all update tiers the same version?
Is there a reason why since WHM 114-ish, all the update tiers (from and including LTS to EDGE) are exactly the same? A "fully tested" build shouldn't be the same as a "development version for testing only and not for production servers". There used to be MONTHS of difference between the STABLE build and the EDGE build. This makes no sense at all, it's like we were always automatically forced to have our production server updating to EDGE.
Also, how do you disable updates? I don't want the server to update during a week day. It makes no sense whatsoever and it makes me very anxious.
-
Hey there! No, it's really not like that at all - this just happens to be the time of year when everything lines up, which often happens with the new LTS release. Check back next March and you'll likely see 124 or 126 doing the same thing.
To completely disable updates, you can follow the details here: https://support.cpanel.net/hc/en-us/articles/360052313594-How-to-customize-cPanel-s-Update-Preferences-from-the-Command-Line
0 -
I don't understand how EDGE can be the same as LTS. It makes no sense whatsoever and I have never, ever seen LTS, STABLE and EDGE be the same value ever in more than 11 years using cPanel. I remember EDGE being at least 1 or 2 major releases ahead of STABLE, let alone LTS. How can a build that has never even been tested instantly be both LTS, STABLE, CURRENT and EDGE all at the same time?!
0 -
I'm not sure how it doesn't make sense. We just haven't released a new version of Edge since 118 made its way through the tiers. We'll be releasing 120 to Edge on Tuesday so it'll change then.
In the top banner here you can see all the release dates:
0 -
LTS and STABLE should have been tested for like 6 months in EDGE before hitting the stage of "stable". That's why it doesn't make sense. Remember just 1-2 years ago when cPanel used to still tag their EDGE releases as .9999 instead of .0?
WHM interface clearly states that EDGE should not be installed on production servers. Yet, it's the same exact major and minor version number as STABLE. How is this making any sense whatsoever?
Thanks for the link above, though is there a way to have WHM update only once a week, say like only on saturdays? Who wants to automatically have EDGE installed on a tuesday morning?!
0 -
I don't believe there is anything I can say that will make you feel better about this. What I can say is that we've generally moved to smaller release cycles so we can aim for quarterly releases. 118 started this year, followed by 120, etc, LTS always happens in March, gets retired in July, etc. The smaller releases means things are much more scheduled and a version doesn't need to linger for 6 months to reach stable.
0 -
118.0.4 has only been released 3 weeks ago. I don't think 3 weeks is long enough to qualify as STABLE. In any case, are you guys pushing this update to all tiers at once because of a security flaw that was patched since 118.0.3 which doesn't even appear in the Change Log? I would understand a little better if you told me so.
0 -
No, that isn't the case. It's just our normal update process.
Each minor version doesn't need to stay in the lower tiers that long.
0 -
OK and what changed in 118.0.3 then?
0 -
As you said yourself, there is no 0.3. If it's not in the changelog it doesn't exist.
I can confirm there is no conspiracy at work here with our version numbers.
0 -
lol I'm not implying any conspiracy. I'm just shocked that I woke up in the middle of the week being on EDGE when I specifically choose to be 2 releases BEHIND current... on a production server. That's all. I don't think you understand the level of anxiety this causes when your WHM interface tells you specifically that the version you were automatically pushed on SHOULD NOT BE INSTALLED ON A PRODUCTION SERVER. It says in BOLD characters too, not even in normal font.
0 -
Don't think about it as "Current" being the same as "Edge" - think about it as "Edge" not receiving updates for so long, its contents became stable enough to become Current.
0 -
lol
0 -
Gonna lock this one now.
0
Post is closed for comments.
Comments
13 comments