You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally, I'm a fan of semantic versioning, but it's ultimately your call.
(" three-part version number: major version; minor version; and patch. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward-compatible, API features, and the major version is incremented for API changes which are not backward-compatible")
The text was updated successfully, but these errors were encountered:
Yes, I am a fan of that system as well. We could work on dev_x.x branches and then merge them into master or a branch called prod_x.x or something like that.
We should have a version number.
Personally, I'm a fan of semantic versioning, but it's ultimately your call.
(" three-part version number: major version; minor version; and patch. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward-compatible, API features, and the major version is incremented for API changes which are not backward-compatible")
The text was updated successfully, but these errors were encountered: