Help understanding cPanel Change Logs

sneader

Well-Known Member
Aug 21, 2003
1,178
57
178
La Crosse, WI
cPanel Access Level
Root Administrator
Hmmm... thanks for trying! But that link leads to a description of the 10.9.0 (build 35) STABLE Tree update, from back in September... over and over and over.

My guess is that you got to that link by inputting something to a CGI script, and by me just accessing the script, I'm not seeing the same thing as you.

Rather than supplying a direct link, can you tell me what steps I would take to be able to view the Change Logs for the Stable Tree?

Thanks!

- Scott
 

randomuser

Well-Known Member
Jun 25, 2005
147
0
166
You're not really missing anything - the main changelog is at changelog.cpanel.net. The one at http://changelog.cpanel.net/changelog/ChangeLog.cgi hasn't been updated in quite a while (you could say the same about the one at changelog.cpanel.net).

In other words, there is no officially updated changelog for cPanel. If you don't see what you're looking for at changelog.cpanel.net, then it's probably not documented, and the best thing you can do is to note which files were changed/added after a upcp, then start diffing.
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
cPanel releases don't actually work that way. That's a misnomer. There is only one version of cPanel (OK they forked it for v11 with EDGE, but bear with me). There are, however, different trees, or milestones that are called STABLE, RELEASE, CURRENT, EDGE and BETA that allow you to stay at a particular version number that cPanel dictates. So, any and all changes up to a version occur in any tree at that version number.

As the changelog stands as of now, STABLE has all the changes listed as STABLE RELEASE and CURRENT are effectively at the same version.
 

sneader

Well-Known Member
Aug 21, 2003
1,178
57
178
La Crosse, WI
cPanel Access Level
Root Administrator
Hi Jonathan. First, thanks for all that you do for the cPanel community... helping here in the forums, and for reasonably priced, quality cPanel server admin services.

OK, so currently my servers are on 10.9.0-S119. This means I'm on STABLE 119.

If I go to http://changelog.cpanel.net/, I see (as of Dec 30, 2006):

10.9.0 (build CURRENT) - 117 Tree
Fri Dec 22 20:08:29 2006
Resolved mis-configuration of Squirrelmail for servers using mbox mail setups.

10.9.0 (build CURRENT) - 114 Tree
Thu Dec 21 21:15:12 2006
Resolved issue where cPanel users were able to add unregistered domains in spite of Tweak Settings value disallowing that ability. Loosened domain name restrictions to allow creation of some non-typical valid domain names.

... (snip) ...



So, questions are:

1) This means that cPanel hasn't gotten around to updating the Change Log, correct? i.e. I am on 119, and the ChangeLog only goes as far as 117. Right?

2) Since I am on STABLE 119, this means that everything listed in the ChangeLog is taken care of, right? i.e. forget STABLE/CURRENT/RELEASE... just look at the build number. If I was on STABLE-75 and I wanted the changes listed in CURRENT-117, I'd just upgrade to STABLE-117 (or go to the latest STABLE). Right?

The hardest thing for me to understand is that if they make a change in RELEASE, I thought that they let it cook for a while before making that same change in CURRENT... then they let it cook a while longer before making that change in STABLE. Clearly I don't understand how it really works!

- Scott
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
1) This means that cPanel hasn't gotten around to updating the Change Log, correct? i.e. I am on 119, and the ChangeLog only goes as far as 117. Right?
If you see consecutive version numbers between the STABLE/RELEASE/CURRENT it usually means that they are the same release code. They increment the number for each tree released. So, in this case, it would suggest that they're all effectively on the same code base.
2) Since I am on STABLE 119, this means that everything listed in the ChangeLog is taken care of, right? i.e. forget STABLE/CURRENT/RELEASE... just look at the build number. If I was on STABLE-75 and I wanted the changes listed in CURRENT-117, I'd just upgrade to STABLE-117 (or go to the latest STABLE). Right?
Right.