Changelog?

[NightStorm]

So wheres the *real* changelog? A new EDGE release was put out today, but there is nothing in the Changelog on layer2.cpanel.net and nothing on the changelog in my WHM that tells me what I should be watching in the ways of new features or potential bugs.
Are they holding out on us?

Oh, and for those who are eyeing it up and wondering... no Apache 2.x yet, and no transfer agent update. Soon though... soon...

[NightStorm]

Another new EDGE release, still nothing in the changelog. What gives?

[NT]

It'd be good if cPanel provided more information in the changelog, as there's not much to tell us what's new/fixed/removed, etc.

[NightStorm]

More information? You mean ANY information, don't you?
There have been no updates to the changelog at all in several releases... this makes it harder to monitor changes to the system in order to figure out where possible bugs may come up.
Can someone from CPanel (I know you're here ) please PLEASE update the changelog more frequently with what I actually have installed on my servers?

[cpanelben]

The lapse in reporting change is unacceptable. This too will change in the near future. Our entire build system is in the process of being reformulated and this change is in mid phase. The changelog changes are an important component of this reformulation. It will work in conjunction with a revamped and extended WHM news replacement that we're calling our messaging center. There will also be an option to feed your end users information about changes and additions to the cPanel interface with references to our expanding documentation.

This topic has always been a sore point with cPanel, so please be assured that we're working to deliver an outstanding solution.

[NightStorm]

My faith in CPanel is renewed (I knew you were watching ). At the moment, is there anywhere at all I can go to be kept up to date on the changes in today's 2 builds, and so on? A file included in the package, or something maybe? or am I stuck waiting until the new system is in place?

[DDT]

I just wonder why we can't get changelogs on anything but edge & beta anymore. I like to know what release is doing, It had a bunch of changes last night but who can know what?

[rpmws]

yea it's been like that a while now. They update the changelog about every 20-30 builds. right now I have a issue with a couple boxs ..anyone see thing on rh3 boxes?

XML::SAX is up to date (0.14).
XML::Simple is up to date (2.14).
perlmod--Install done
GD installed ok
initfpsuexec: using apache 1.x support
Testing connection speed...(this could take a while)....Done
Ping:3.376 Invalid Url at /scripts/cPScript/MirrorSearch.pm line 145
cPScript::MirrorSearch::_testmirrorspeed('undef') called at /scripts/cPScript/MirrorSearch.pm line 109
cPScript::MirrorSearch::_fetchgoodhosts('layer2.cpanel.net', 10, 5, 'HASH(0x829ffac)', 'HASH(0x829ff28)', 0) called at /scripts/cPScript/MirrorSearch.pm line 68
cPScript::MirrorSearch::findfastest('days', 10, 'key', 'layer2.cpanel.net', 'count', 5, 'urls', 'ARRAY(0x82d7070)') called at /scripts/cPScript/HttpRequest.pm line 224
cPScript::HttpRequest::_getAddressList('layer2.cpanel.net') called at /scripts/cPScript/HttpRequest.pm line 52
cPScript::HttpRequest::request('cPScript::HttpRequest=HASH(0x83078c8)', 'host', 'layer2.cpanel.net', 'url', '/EDGE-installer/', 'protocol', 0) called at /scripts/upcp line 328

[chirpy]

I just wonder why we can't get changelogs on anything but edge & beta anymore. I like to know what release is doing, It had a bunch of changes last night but who can know what?

That's a misnomer. There is only one version of cPanel. 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. The fact that the changelog isn't being updated is, of course, the real issue

[DDT]

Having used both Stable & release in the "old days" your WHM changelog would only show the changes in whatever version you were running, so running release tree you wouldn't see all the edge & beta stuff that meant nothing to you anyway. Now you see nothing EVER about release, only Beta & Edge.
Last night was a perfect example, something in the cPanel update conflicted with Clam and ALL my e-mails were blocked for about 4 hours until we sorted out the problem...no way of knowing what caused it... but I know there was a change in WHM because now I have a "secure site" login at the top which then tells me I have no security certificate (I guess I should buy a security certificate for each server where nobody but admins will ever see them...duh) that wasn't there before...but look at the changelog & nothing...so who knows what.
The change logs should detect what tree is being updated (the updates do anyway) and display the relevant changelogs. Simple.

[chirpy]

You've completely missed the point of what I said.

The fact that the changelog isn't being updated aside...

There is only one version of cPanel. If you look at the changelog it shows that one version. There are multiple milestones that cPanel dictates as I mentioned. So, if you're running RELEASE vx.y.z then allthe updates up to and including that version in the single version changelog apply to the milestone you are running on.

[NightStorm]

And, when all is said and done, we will simply wait with substandard changelog updates until the new system is put in place.
Why? Because CPanel is worth the wait.

[chirpy]

I'm on the edge of my seat It'll come as a welcome relief to see proper documented changes.

[DDT]

You've completely missed the point of what I said.

There is only one version of cPanel. If you look at the changelog it shows that one version. There are multiple milestones that cPanel dictates as I mentioned. So, if you're running RELEASE vx.y.z then allthe updates up to and including that version in the single version changelog apply to the milestone you are running on.

I'm tired of missing your point, I have only been using it for 4 years or so (only panel I have used in so long I can't remember) so I can't possible know anything about "one version of cPanel" (I tried to make it clear I understood development trees)

OK, So the last 2 nights release updated versions (big one night before last from R57 to R63 in one big jump), but nothing in the changelog shows "release" so how do I know which of those beta or edge changes that ARE there are incorporated into what it did to my release version between 57 & 63? Something in there screwed with Clam, but who knows what?
No numbers match etc. so since no version numbers match and nothing says release PLEASE make it more clear to this idiot how I tell what they did to release night before last?
It had to be big to jump 6 "R" numbers in one nightly update...but no mentions at all in the changelog

[NightStorm]

Well, I'm noticing some edits, so I'll refrain from tackling an exact reply. About all I can offer is that CPanel likely has several people all developing at once, which can make it easy to lose track of changes and updates when not using a proper project manager interface... this would likely explain the lack of update notices. Definately a downfall, but it's one they are in the process of correcting, so I won't call further attention to it.
As for the massive jumps in builds, you need to keep in mind that they have been averaging at least 2 EDGE releases per day for the last 4 days... so it's likely that while you may have only seen the one big jump, it was in fact a series of smaller jumps throughout the course of the day.
And on a side-note, I do see a few small mentions of changes in the log... still very unlikely to be all the changes that were made, but I have to give CPanel credit for at least listening to their customers and acting on requests... something that certain other control panels have lost the ability to do since releasing their most recent build (*cough*8.0.0*cough*).
Its my guess that with an update to the STABLE release (rumor on the board is that it's coming tomorrow), CPanel will have some time to focus more on the side projects, like keeping track of update changes, and at that time we can begin to see a much better CHANGELOG system.