cPanel 70 Release Status

[Nirjonadda]

I have get one email from cPanel about version 70 CURRENT Releases in Week of Jan 22 then Get another email about version 70 CURRENT Releases in Week of Jan 29. Now get one new email about version 70 is now in CURRENT but v70 still are in EDGE. So Please can we ask that why this type confusion or pain are continued given their clients?

 

[cPanelUser-Inactive]

We're so sorry for the confusion! We have been forced for a few reasons (most recently by bugs in our upstream providers) to delay version 70 much longer than we desired, and it looks like the copy for the newsletter wasn't updated to reflect that delay.

 

[Nirjonadda]

We're so sorry for the confusion! We have been forced for a few reasons (most recently by bugs in our upstream providers) to delay version 70 much longer than we desired, and it looks like the copy for the newsletter wasn't updated to reflect that delay.

Then Please let's me confirm that when will be release v70 in current?

 

[cPanelUser-Inactive]

Then Please let's me confirm that when will be release v70 in current?

Unfortunately, we don't yet have a definitive date of release, but we are hoping to see it next week.

A little more information: We were hoping to upgrade to Dovecot 2.3.0 in version 70, but encountered a bug when we upgraded our mail server. We are currently waiting on a bugfix from Dovecot for that bug, but we have a plan that will hopefully let us get v70 out to CURRENT next week, with or without that bugfix.

Hopefully that helps!

 

[sparek-3]

Was the Dovecot bug not found in Edge?

Is there anybody actually using Edge?

What's the point of having Edge if nobody is using it and finding these bugs? It's a bit concerning that 70 was all prepped and ready to go to CURRENT when ... "woops! found a bug"

Granted 70 was never pushed out to CURRENT - so I suppose I'm making my own argument against this argument. And CURRENT is still a tier away from RELEASE. But how many more bugs are going to be uncovered when 70 hits RELEASE and STABLE?

It just seems that something needs to be done in regards to how testing is done and general QA.

 

[cPanelUser-Inactive]

Was the Dovecot bug not found in Edge?

Is there anybody actually using Edge?

What's the point of having Edge if nobody is using it and finding these bugs? It's a bit concerning that 70 was all prepped and ready to go to CURRENT when ... "woops! found a bug"

Granted 70 was never pushed out to CURRENT - so I suppose I'm making my own argument against this argument. And CURRENT is still a tier away from RELEASE. But how many more bugs are going to be uncovered when 70 hits RELEASE and STABLE?

It just seems that something needs to be done in regards to how testing is done and general QA.

Yup, you're going a little circular there. The bug was found in EDGE, and we specifically didn't push 70 to CURRENT because of its existence. There are a non-trivial number of EDGE servers out there, with people providing us valuable feedback before we go to CURRENT. In this case, though, we found the bug on our own mail server when we upgraded our server, which runs a bleeding-EDGE build. Dovecot version 2.3.0 support was released to the EDGE tier January 16th:

• Implemented case CPANEL-17900: Add support for dovecot 2.3.0.

We have an entire suite of testing that goes on before a version is released, but the strength of our EDGE users is the ability to see the software tested in real-world, non-clean environments. That's how we uncovered the bug in Dovecot, preventing it from getting to CURRENT. We announce our anticipation of releasing new versions to help people be aware of our anticipated changes, but we will hold up a release if we encounter a problem.

 

[sparek-3]

So the bug was found in your own internal servers, not by any of the "non-trivial number of EDGE servers out there, with people providing us valuable feedback before we go to CURRENT."

I don't know. This is just a bit concerning because I'm not able to follow this process.

How long was the bug in the Dovecot version in the EDGE version? And nobody using those non-trivial EDGE servers - with "he ability to see the software tested in real-world, non-clean environments" ran into the issue? Doesn't that kind of question the validity of those non-trivial EDGE servers?

I understand there is a process for releasing different versions of cPanel. But it just seems to me that more and more bugs and issues are coming up in RELEASE and STABLE which just really makes me question how EDGE and CURRENT are being used and really what the point of having EDGE and CURRENT is.

 

[cPanelUser-Inactive]

This is just a bit concerning because I'm not able to follow this process.

I definitely understand your concern, especially without being able to see the process. Any bugs that we identify in EDGE can prevent us from going to CURRENT, but we still have goals for the release timeline. I send out announcements about anticipations of release based on conversations with our release marshalls, but our timeline will be shifted as is needed to ensure the smoothest possible release.

 

[Nirjonadda]

Unfortunately, we don't yet have a definitive date of release, but we are hoping to see it next week.

So Current Tier delayed for 3 time then now over for one month? Do you recommended really we need another control panel for replacement?

 

[rpvw]

I am sorry, but I think the sensationalist and provocative title of this thread is worthy of a tabloid newspaper headline (or the title of one of my threads ).

*****EDIT*****
2 Feb 2018 Glad to see the thread title has now been changed !

As I have expounded on ad nauseum, I would much rather that cPanel delayed their roll-outs, and get them right, than try and meet some accelerated and contrived release schedule that produces buggy code and ill thought out features.

I am actually delighted to see delays for bug removal (hands Benny can of bug spray) but I do agree that some sort of better information disclosure and transparency might be of benefit.

Thanks again cPanel, and do keep us in the loop

 

[sparek-3]

Just to be clear, I'm not upset about the delay in cPanel 70 to CURRENT. As @rpvw says, I'd rather have the bugs solved before moving up a tier.

My concern is more with the process and why these bugs aren't being caught in EDGE or CURRENT or in some cases even RELEASE. I just question what the point of all of these tiers are if major bugs aren't being found until they get into RELEASE or STABLE. Some of the concerns with AutoSSL come to mind.

And now it seems that this lack of attention is filtering in to EA4. There's been a couple of EA4 updates lately that immediately had to have fixes posted to them or reverted shortly after they were released.

Don't misinterpret anything I say, I'm not pointing a blame at anyone. I'm just wondering if more can be done to better resolve some of these quality assurance issues.

 

[rpvw]

Without writing pages of facts about how code developers work (or should work) there are a couple of points that maybe should be acknowledged:

• Users want more, they want the very latest in everything, and they want it now, and they want to pay less for it.
• Developers want to release one set of perfect code every 5 years which is fundamentally incompatible with the wants of users (and especially shareholders and bean counters)
• In today's world, the accountants rule, and everyone has to acquiesce to their dictates.
• Users rarely put on the hat of the developer to try and understand the problems that the developer faces in writing code for an increasing diverse selection of platforms and systems that is changing faster than they can write the code for it.
• Developers are often so busy adding new features and making their code run on the enormously diverse systems that users demand it runs on, that they lose sight of what the user wants (or needs).

There is no easy answer..........it is what it is ............ if we all work together and contribute carefully considered ideas and points of view (and that does not preclude criticism if warranted) we shall all benefit in the end.

 

[rangka_kacang]

For all my concern is to see the availability of 70 to CURRENT or STABLE because I'm now stuck with EDGE tier (upgraded just to fix the SSL bug) and no way to downgrade to 68 (disabling the auto update now). I'm also actually quite thrill to see the announcement that 70 will be pushed next week because it's scary that I accidentally upgraded to EDGE in my production server (due to desperation to tackle a bug); I'm stuck in between the process, I can only wait but the OP has his point too.

 

[Nirjonadda]

We were hoping to upgrade to Dovecot 2.3.0 in version 70

So I think Dovecot downgrade to the previous version 2.2.33.2?

Fixed case CPANEL-18380: Update dovecot to 2.2.33.2-3.cp1162.

 

[rpvw]

70 Change Log - Change Logs - cPanel Documentation
See the bottom line of the change log for 70.0.8 2018-01-31

Fixed case CPANEL-18380: Update dovecot to 2.2.33.2-3.cp1162.

This looks like it represents a reversal from the previous 70.0.6 2018-01-25 that said

Fixed case CPANEL-18270: Update dovecot to 2.3.0-7.cp1162.

I guess we shall have to wait to see if the reversal is reversed (huh?) in 70.0.10

 

[cPanelUser-Inactive]

Yup, you caught it! We've opted to exclude the upgrade in 70, and are working on testing a version of 70 that would be released next week. Right now the plan is to upgrade Dovecot again in 72.

 

[Nirjonadda]

Yup, you caught it! We've opted to exclude the upgrade in 70, and are working on testing a version of 70 that would be released next week. Right now the plan is to upgrade Dovecot again in 72.

So why still are showing here that release this week?

 

[Nirjonadda]

Now get two email about cPanel & WHM version 70 is now in CURRENT.

 

[Thunderchild]

according to my preferences section on updates 68 is current and 70 is on "edge"

 

[Thunderchild]

nice to see my other post was removed, thanks i get the drift!