Why isn't my server updating to cPanel & WHM version 60?

LTOTH

• October 16, 2016 03:43

I have a VPN server with Bluehost that is running version 58.0.32. I have my preferences set to auto-update and I just clicked the update option in an attempt to force a manual update to version 60. It's not updating. It says that I am already running the latest release. How can I force our server to update to version 60? Thanks.

• 

  rpvw

  • October 16, 2016 09:13

  I believe you need your Update Preferences set to the Release Tier you are attempting to upgrade to (eg at time of writing, v60.0.4 is at CURRENT) You might also want to review any Upgrade Blockers that may influence your intended upgrade: please see

  0
• 

  LTOTH

  • October 17, 2016 00:27

  I see it now. CURRENT 11.60.0.4 Release Candidate Thanks.

  0
• 

  LTOTH

  • October 17, 2016 12:50

  So why does my server see it as a "Release Candidate" and not the current release?

  0
• 

  rpvw

  • October 17, 2016 13:00

  Please see Product Versions and the Release Process - cPanel Knowledge Base - cPanel Documentation

  0
• 

  LTOTH

  • October 17, 2016 13:27

  Thanks. I was confused because I thought that version 60 had already been released. So how long does it typically take to go from "Current" to "Release"...days, weeks, months? I normally don't care about using the latest update but version 60 has a feature that we really need on a new server that we are setting up.

  0
• 

  cPanelMichael

  • October 24, 2016 17:15

  Thanks. I was confused because I thought that version 60 had already been released. So how long does it typically take to go from "Current" to "Release"...days, weeks, months? I normally don't care about using the latest update but version 60 has a feature that we really need on a new server that we are setting up.

  
  Hello, Here's the relevant section from the Product Versions and the Release Process - cPanel Knowledge Base - cPanel Documentation document: Production releases As of 2016, our goal is to complete at least four production releases each year with the following schedule: [LIST]

  The first production release around January.

  The second production release around April.

  The third production release around July.

  The fourth production release around October. Production releases use the following process:

  ]
  • We complete development of the production release.
  • We test the functionality of the release's new features.
  • We publish the release to the development tiers, and to the EDGE, CURRENT, and RELEASE tiers. Note: At this point, except for critical security issues, we no longer develop or publish any changes to the previous releases.
  • After the release enters the RELEASE tier, we assess any immediate maintenance needs.
  • After we resolve the immediate maintenance needs, we publish the production release to the STABLE tier.

  
  Let us know if this helps. Thank you.

  0

Please sign in to leave a comment.