In October, we announced our transition to a semi-annual release cadence, which has been well received across the board. After further consideration to further enhance consistency across the Sugar suite, we're adopting a new standardized versioning convention for our products. This change will help simplify versioning and improve end user experience.
Going forward, releases will follow this format:
<Sugar_Product> <Year>.<Release>.<Patch>
For example, the upcoming release will be named Sugar Sell/Serve/Enterprise 25.1.0, replacing the previous quarterly format (e.g., Q2 2025 15.0). This new versioning scheme applies to the following Sugar products: Sugar Sell, Sugar Serve, Sugar Enterprise, SugarCloud Insights, SugarIdentity, Sugar Discover, and sales-i.
Key Points:
- The second number in the release number will be:
"1"for Cloud + On-Premises releases (April)"2"for Cloud-only releases (October).
- The calendar quarter reference will be dropped from the versioning convention.
- The upcoming release will still meet the original GA date of Mid-April 2025.
- The Release Preview will be delayed to Mid-March but still give you enough time to test your customizations before the official release.
What Does This Mean for You?
There will be impacts on developers that build or maintain Module Loadable Packages. Read on for details about what you can expect with this change:
Why are we updating the versioning convention?
SugarCRM is streamlining versioning across Sugar products to make it easier for our customers to track and manage releases. While this standard versioning convention has been adopted by some of our products, it will now be extended across even more products for more consistency.
Which products are affected?
The new versioning convention will apply to :
- Sugar Sell
- Sugar Serve
- Sugar Enterprise
- SugarCloud Insights
- SugarIdentity
- Sugar Discover
- sales-i
What will happen during and after the upgrade?
As always, when new packages are uploaded, they will go through our Package Scanner to verify compatibility with the new release. For this upcoming release, the version number will be 25.1.0.
Pre-installed packages won’t be impacted by this change, and no additional actions will be required on your part for those.
When is this happening (plan and timeline)?
- Release Preview: Mid-March 2025 (delayed to allow extra testing time by the Sugar Engineering team)
- General Availability (GA): Mid-April 2025 (as planned)
What action do I need to take with my MLPs?
To ensure compatibility with this release, make sure your customizations are up-to-date, as this release (see release preview documentation for list of changes) that are unrelated to the version change.
If you’re using Module Loadable Packages (MLPs), be sure to update the versioning in your MLP's supported version list. In your planning and in your package code, you may have anticipated the next Sugar release version to be 15.x. The next version you should use in your packages should be 25 and not 15! For example, if you use 25.*, your package will be compatible with all releases throughout 2025.
What’s Changing in the REST API?
The good news is that API endpoints won’t see any major changes outside of the regular version bumps to the REST API. So, if you’ve already tested against previous versions, your integrations should remain stable.