New Gainsight Release Cycle for Better Prep and Quality Experience

  • 11 December 2021
  • 15 replies
  • 389 views

Badge

What’s that you say? Move to a quarterly release cycle?

 

We hear you loud and clear. A time-based quarterly release cycle is definitely the right call, and we’re preparing to take action based on your input. In fact, Gainsight’s adoption of this global strategy for quarterly product releases is expected to start in April/May of 2022. 

 

Key Benefits of Quarterly Release Cycle [win-win]:

You...

Gainsight...

Get early head’s up about the upcoming changes 

Gets longer time to perform testing activities such as performance testing and UAT, hence, improves the quality

Get more time to make necessary arrangement to embrace the changes

Forecasts detailed planning via roadmap efficiently 

Spend adequate time to explore Beta features and provide feedback

Implements feedback and gets aligned with the incremental beta feature development strategy

Experience better quality and improve adoption

Spends more time to review the change rate at the end of each quarter and make necessary adjustments

Improve synergy and get engaged on Community discussing about a specific release/enhancement and sharing inputs

Provides better approachable and manageable end goals to ensure customer success

The time between the two major releases will be pretty long, to fill the gap and continue pushing minor changes into the production orgs, we will be having more number of patch releases. These patch releases will typically contain escalations/known issues [with resolutions/with or without workarounds] and minor enhancements. [Sample patch release notes]. The patch release dates will be communicated to you as soon as the list is ready.

 

IMPORTANT: All significant enhancements and new features will be shipped to our customers with the major releases.

Note: Version numbering will not be impacted. For more information about the release dates (2022 Release Calendar), customer communication plans etc, refer to the following documents:

* Jan/Feb 2022 release dates have been pushed back by a week. The dates are now updated in the above mentioned release process documents.

We’re sure that you’ll have an all-round smoother experience with the implementation of Quarterly Release cycle! Share your thoughts with us via Community

 

Thanks

FYI @minh_phan @anirbandutta-test-user @chuck_girard @sidhu @mahesh_patil @siva_prasad_nasika @courtney_hauser @lane_h @SeanDonnelly 


15 replies

Userlevel 5
Badge +8

:clap_tone2:  Thank you!  Thank you!  Love, love, love, the advance copy of release notes and longer cadence between releases.  Will we also have the releases in our sandbox environments around when the notes are available prior to the production release?

Userlevel 7
Badge +3

Will we also have the releases in our sandbox environments around when the notes are available prior to the production release?

Yes, we want to know this as well!

Userlevel 7
Badge +2

@neelam_mukherjee would you be able to shed more light here about the sandbox environment releases?

Badge

Adding @kendra_mcclanahan & @sidhu for more information on Sandbox Environment.

Userlevel 7
Badge +3

@neelam_mukherjee a few questions:

  • when should we be expecting the “early head’s up about the upcoming changes” ahead of each quarterly release?  Since these releases will likely contain more changes, I would expect we’d have a longer lead time on notification. 
  • on what cycle/cadence will Patch Releases occur?  Since we don’t receive a push notification on these, we need to know when to go and look for them.
  • Any updates on the Sandbox Environment question? @kendra_mcclanahan @sidhu ?
Userlevel 7
Badge +2

+@jake_ellis, @dstokowski in the convo 

Badge

Hi Jeff @darkknight
Thanks for reaching out!
1. We’ll be sending the High-Level Product Release Summary list document by 6-7th April (through emails, engagements, and Community). Next release onwards we will share the info even earlier.  @courtney @chuck_girard @suresh_kumar

2. Patch Releases will occur as and when required. Docs team quickly captures the changes/fixes in the Patch Release Notes and make it available on the day of patch release (prod deployment).
(Total number of patch releases may vary - adding @madhu here for more details]
Note: If you are on NXT and admin, you can see the latest docs list in our Knowledge Center Bot in the application (only for admins areas). If not, you will find the info here and we’ll update soon after the patch release notes are published .

 

3. @kendra_mcclanahan for the Sandbox Environment question

Userlevel 7
Badge +3

Hi Neelam thanks for the update.  Additional question on 2:

 


2. Patch Releases will occur as and when required. Docs team quickly captures the changes/fixes in the Patch Release Notes and make it available on the day of patch release (prod deployment).
(Total number of patch releases may vary - adding @madhu here for more details]
Note: If you are on NXT and admin, you can see the latest docs list in our Knowledge Center Bot in the application (only for admins areas). If not, you will find the info here and we’ll update soon after the patch release notes are published .

 

Whenever patch release is required, is there a specific day/cadence for when those are released?  It’s not a great user experience to expect us to check the docs site every day, waiting to see if/when something has been released.  

We either need to know that they will be released on a regular cadence, so we know when to check, or we need to receive a push notification that it has been released.

Badge

Hi @neelam_mukherjee, Jeff @darkknight,
As you know, we do not have any planned patches and we are not planning to enable any major functionality during the patches, we do not have any planned dates for those.

On this request from Jeff - "we need to receive a push notification that it has been released."
One approach can be, we can publish the notes in a site and notifications will be received once subscribed to that site. @neelam_mukherjee will share more details on the approach.

FYI - @neelam_mukherjee  also confirmed that all patch release documentation (between 2 major releases) is referred as links and included in Next Major release.

Userlevel 7
Badge +3

@madhu  I know you’re not “planning to enable any major functionality during the patches” but as noted in the original post “The time between the two major releases will be pretty long, to fill the gap and continue pushing minor changes into the production orgs, we will be having more number of patch releases. These patch releases will typically contain escalations/known issues [with resolutions/with or without workarounds] and minor enhancements.”

 

Bottom line: Anytime a change is made to Gainsight, admins need to be aware of what those changes are. Even the smallest enhancement can catch us by surprise if we were not aware of it.

 

@neelam_mukherjee I look forward to learning what those communication channels will be.

Userlevel 7
Badge +6

 

Bottom line: Anytime a change is made to Gainsight, admins need to be aware of what those changes are. Even the smallest enhancement can catch us by surprise if we were not aware of it.

 

@neelam_mukherjee I look forward to learning what those communication channels will be.

 

I would also add that ‘enhancements’ also contain a shocking number of reductions in functionality that are too often glossed over. Having admins find out the hard way is not great.

Badge

Hi,

  • We usually publish the patch release notes related information in Community > Product News category & internally too. If you subscribe to such post, you will receive the notifications related to specific series of patch release notes that go out before our next major release. 
     
  • The patch release related information  will also be available in the immediate next major release notes under the Additional Resources section. 
     
  • If not opted out from receiving PX engagements/KC BOT, NXT Admins will be able to see the patch release information in the PX’s Knowledge Center (KC) Bot > What’s new category in NXT org soon after the release. 

FYI @sakumar @Divya  

Userlevel 7
Badge +6

Hi,

  • We usually publish the patch release notes related information in Community > Product News category & internally too. If you subscribe to such post, you will receive the notifications related to specific series of patch release notes that go out before our next major release. 
     
  • The patch release related information  will also be available in the immediate next major release notes under the Additional Resources section. 
     
  • If not opted out from receiving PX engagements/KC BOT, NXT Admins will be able to see the patch release information in the PX’s Knowledge Center (KC) Bot > What’s new category in NXT org soon after the release. 

FYI @sakumar @Divya  

Hey @neelam_mukherjee you’re right in that patch notes are communicated out. The main ask rather is that they be communicated with the same level of transparency and proactive methodology that regular releases are.

Badge +1

An update on the Sandbox Environment question -  “Will we also have the releases in our sandbox environments around when the notes are available prior to the production release?”

  • For our SFDC Edition customers, first all Salesforce Sandbox orgs were upgraded and then the production orgs were upgraded 2 weeks later. Since around Dec 2020 we have changed this and have been upgrading all production and sandbox orgs on the same day.
  • For our NXT customers, all Sandbox and Production tenants were always upgraded on the same day. 
  • We do not have any plans of changing this now. We are going to be upgrading both sandbox and production instance on the same day even with the move to quarterly releases.
Badge

📢 We’re ready with the High-Level Product Release Summary List (NXT & SFDC) documents which will be shared with you all by tomorrow via Emails and In-App Engagements. 

 

FYI @anirbandutta @sakumar 

Reply