A Simpler, More Consistent Versioning Scheme for Sugar Products

At SugarCRM, we’re always looking for ways to simplify processes and improve your experience. Recently, we updated our product release cadence to better align with customer needs. Now, we're adjusting how we number new releases for clarity and consistency.

Starting with our April release, we’re moving to a standardized versioning format:

<Sugar_Product> <Year>.<Release>.<Patch>

For example, our upcoming CRM release will be Sugar Sell/Serve/Enterprise 25.1.0, replacing the previous quarterly format (e.g., Q2 2025 or 15.0). This change ensures consistency across more of our products, including:

• Sugar Sell
• Sugar Serve
• Sugar Enterprise
• sales-i
• Sugar Market
• SugarCloud Insights
• SugarIdentity
• Sugar Discover
• ...and more to come

What You Need to Know

• No impact on release dates or cadence—just a clearer way to label versions.
• New versioning structure for Sell, Serve, and Enterprise:
  • “.1” for Cloud + On-Premises releases (April)
  • “.2” for Cloud-only releases (October)
• New versioning structure for all other products:
  • “.1” for the first release of the year
  • “.2” for the second release of the year
  • and so forth
• No action required—this won’t affect pre-installed custom packages in Sugar Sell, Serve, and Enterprise.
• Developers should review Updates to our Release Version Convention that affects Module Loadable Packages in DevClub to understand changes affecting Module Loadable Packages.

To stay updated, follow Release Central on SugarClub for an overview of what’s new every April and October (in conjunction with the Sell and Serve releases) or subscribe to our Product Update blogs for detailed insights.

Have questions? Drop them in the comments below!