SCM release version convension, major minor patch build

<major>.<minor>.<patch>.<build>
e.g 1.0.1

  • Major versions must increment when significant changes or breaking changes are made
    • Examples: 
      • Remove a method
      • Change a signature
      • Change a return type
      • Remove an API
  • Minor versions must increment when minor additions are made that and backward compatibility is maintained
    • Examples: 
      • add a new method
      • add a new variable
      • add enhancement
  • Patch versions are incremented when functional (inner method) changes are made to fix behavior problems
    • Example: 
      • Change the business logic or a method to perform calculations differently
  • Build versions are incremented when new build is created

No comments :

Post a Comment