Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. To meet our high quality standards for AWS deployments of Clarity, we reserve time after the initial release of a major version of Clarity to ensure stability, scalability and security of the release in AWS. We target the availability for deployment of a new major release into AWS Non-PROD environments two weeks after release date, and PROD environments a few weeks after that. Although new releases will be available within 2 weeks, we Recommend waiting 6 weeks for the first patch to be available as a best practice. For example, v15.9.1 was released February 8th, and AWS clients can start upgrading non-PROD environments after February 23rd. The first Clarity v15.9.1 patch is targeted for release on April 1st. Please submit a ticket to initiate the scheduling process.

  2. Rego maintains a comprehensive disaster recovery and restoration program.  Production Clarity environments are backed up immediately prior to upgrades in the event a future roll back is necessary.  After a PROD upgrade is complete, any issues that cause a full outage may be logged as a new Sev1 support ticket.  If the issue cannot be resolved within 24-hours, a roll back plan may be initiated.

  3. Rego conducts roll back plans with a prescribed approach to ensure a high likelihood of success.  Rego has closely managed the Clarity upgrade planning and execution for hundreds of Clarity customers, rollback plan initiation is extremely rare. The Rego subject matter experts, engineers and support staff are available 24x7 to provide heightened support of the upgrade, ensuring all Sev1 issues are remediated and mitigated promptly.  In the extremely unusual circumstance that a roll-back plan is required, Rego retains the ability to roll back on the first full business day after the PROD upgrade – this option includes the likelihood of a full business-day of outage.  Roll-back plans may be initiated if you or Rego encounter a production issue that results in a projected outage of 24 hours or more during business hours while the issues is investigated and remediated.  Any roll-back execution would be discussed and approved by Rego leadership.

  4. Rego recommends customers remain current on their upgrades by executing at least one upgrade per year. In the event you are using a version of Clarity that is near it’s end-of-life cycle from Broadcom, Rego will support you for 3 months beyond the EOL data at zero additional cost. Beyond 3 months we will charge an additional 25% monthly subscription rider fee, plus a one-time fee to execute the upgrade, when appropriate, due to the large gap in versions.

Upgrade Schedule for Clarity

...

SaaS:

The following table contains customer upgrade schedules for the upcoming Clarity SaaS releases. These are targeted dates and minor adjustments to the schedule may occur.

Clarity Version

Target Release to On-Premise

Target Release to GCP SaaS Non-Prod

Target Release to Available for Scheduling in AWS SaaS Non-Prod

Target Release to GCP SaaS Prod

Target Release to Available for Scheduling in AWS SaaS Prod

15.9.0

Nov 9th 9th 2020

Nov 24th 2020

Dec 8th 8th 2020

Dec 13th 13th 2020

Dec 28th 2020

15.9.1

 Feb 8th 8th 2021

Feb 23rd 2021

Mar 9th 9th 2021

Mar 14th 14th 2021

Mar 29th 2021

15.9.2

 

 

 

 

  May 23rd 2021

 May 31st 2021

 Jun 18th 2021

Jun 28th 2021

15.9.3

 

 

 

 

  Aug 22nd 2021

 Aug 30th 2021

 Sep 17th 2021

 Sep 27th 2021

16.0.0

 

 

 

 

  Nov 15th 2021

 Nov 22nd 2021

 Dec 10th 2021

 Dec 20th 2021