Skip to main content
Software Engineering

Return to Answer

Commonmark migration
Source Link
Community Bot
Community Bot
  • 1

You could modify the practice of Major.Minor.Build.Revision to something more like Major.Minor.Release.Revision. See examples:

1.0.0.0 - First Release

 

1.0.0.123 - Beta build approaching second release

 

1.0.1.0 - Next release

 

1.0.1.234 - Beta build approaching third release

 

1.1.0.0 - Third release

etc..

You could modify the practice of Major.Minor.Build.Revision to something more like Major.Minor.Release.Revision. See examples:

1.0.0.0 - First Release

 

1.0.0.123 - Beta build approaching second release

 

1.0.1.0 - Next release

 

1.0.1.234 - Beta build approaching third release

 

1.1.0.0 - Third release

etc..

You could modify the practice of Major.Minor.Build.Revision to something more like Major.Minor.Release.Revision. See examples:

1.0.0.0 - First Release

1.0.0.123 - Beta build approaching second release

1.0.1.0 - Next release

1.0.1.234 - Beta build approaching third release

1.1.0.0 - Third release

etc..

Source Link
Adam Maras
Adam Maras
  • 381
  • 2
  • 9

You could modify the practice of Major.Minor.Build.Revision to something more like Major.Minor.Release.Revision. See examples:

1.0.0.0 - First Release

1.0.0.123 - Beta build approaching second release

1.0.1.0 - Next release

1.0.1.234 - Beta build approaching third release

1.1.0.0 - Third release

etc..