Understanding release numbers

PreBilt for Public Cloud uses a three-part version numbering format:

Major.Minor.Patch

e.g., 3.5.2

Version Element	Example	Meaning
Major	3	Significant new functionality, platform changes, or major enhancements that may require additional testing and user communication.
Minor	5	New features, improvements, and enhancements that are backward compatible with existing processes.
Patch	2	Bug fixes, performance improvements, and small corrections with minimal functional impact.

Typical Upgrade Guidance

• Patch releases should require limited regression testing. This could be upgraded to when possible.

• Minor releases should be tested against key business processes before deployment. This should be upgraded to at the earliest convenience.

• Major releases should undergo full user acceptance testing and deployment planning. This must be upgraded to within 6 months of release otherwise some functionality could break, due to SAPs deprecated APIs.