MuleSoft will be releasing updates aligned with Salesforce releases to give developers greater flexibility and more convenient timeframes …
Here are highlights from article Introducing the Next-Gen Mule Runtime Release Cadence
1. Transition to regular release cadence:
– MuleSoft is moving from an ad-hoc release cycle to a regular release cadence of three times each year (Winter, Spring, Summer).
– This aligns with the Salesforce release cycle and enables joint customers to plan and manage upgrades more efficiently.
2. Introduction of new release channels:
– Two new release channels are being introduced, Long-Term Support (LTS) and Edge.
– LTS versions are released annually in February and provide longer application maintenance periods.
– Edge versions are released every four months and focus on enabling faster innovation.
3. Support windows for each release:
– Edge versions have a support window of 4 months, while LTS versions have a support window of 12 months.
– Both Edge and LTS versions will receive regular patches for security vulnerabilities and critical issues.
4. Recommended use cases for each release channel:
– LTS is recommended for mission-critical applications and on-premises runtime deployments.
– Edge is recommended for organizations or applications that require the latest features and advancements and have the resources to manage more frequent upgrades.
5. Change in versioning scheme:
– Mule Runtimes will continue to receive monthly updates, but will follow a new versioning scheme.
– The Hybrid Standalone deployment model will move from date-based versioning to semantic versioning (Major.Minor.Patch).
– CloudHub 1.0, CloudHub 2.0, and Runtime Fabric will use the Major.Minor.Patch:Build versioning schema, with “e” for Edge releases and blank for LTS releases.
You can read it here: https://sfdc.blog/jfFGc
Source from developer(dot)salesforce(dot)com