CRM - Release Cadences (Streams)

Type of Release

Scope

Testing Needs

Bug Fixing

Excludes: Non-urgent changes that can be released as part of weekly/monthly, to be evaluated by the product owner / TL. Access management (permission sets, profiles, approval processes, queues), unless it is the originator of the bug.

Includes: (upon proper justifications given by product owner / TL: 

Bug Fixing - TODO: Reference what is a bug documentation.

To be evaluated according to complexity of the fix

Minor

Excludes: Backend Code and flows and Process Builders that could a regression and affect monthly (to be analysed by RM & Tech Lead on tech perspective)

Includes: (Cosmetic Changes) LWC Front-end (html and css, except javascript) Page Layouts, Labels, SOQL, validation rules, assignment rules, approval processes, new fields (if no mandatory fields (so impacting test factory and sandbox seeding), email templates, email alerts, content of Custom Settings and Custom Metadata, Report Types, Reports & Dashboards, sharing rules, public groups, queues, role hierarchy, permission sets, profiles, quick links, compact layout, quick actions,  search layouts, list views, Home page.   

This will NOT require NRT every Minor release, but

will require NRT Monthly

Business Acceptance Test

Major

Excludes: Changes with high impact across different areas of the org which cannot be done within 3 weeks period and must be released as a single unit, for example, redesign/reimplementation of OWD and sharing/security model (such as PO2, CMSplit projects). To be evaluated during Project preparation.

Includes: Any kind of change whose impact can be controlled (within a defined application scope) and tested during the INT & UAT timelines defined in the Release calendar

Functional Test, NRT, E2E Test, IT UAT Readiness, Business Acceptance Test

Long Run

Includes: Changes with high impact across different areas of the org, for example, redesign/reimplementation of OWD and sharing/security model (such as PO2, CMSplit projects). To be evaluated during Project preparation.

Same as Monthly release but with extension in the duration of the testing and in which orgs the testing is carried.
To be evaluated according to complexity of the fix