Follow Semantic Versioning in Releases #13

Open
opened 1 year ago by gytisrepecka · 1 comments
Owner

Follow Semantic Versioning in application Releases.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards compatible manner, and
  • PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Follow [Semantic Versioning](https://semver.org/) in application [Releases](https://source.gyt.is/gytisrepecka/webimg/releases). > Given a version number MAJOR.MINOR.PATCH, increment the: > > * MAJOR version when you make incompatible API changes, > * MINOR version when you add functionality in a backwards compatible manner, and > * PATCH version when you make backwards compatible bug fixes. > > Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
gytisrepecka changed title from Follow Semantic Versioninf to Follow Semantic Versioning in Releases 1 year ago
gytisrepecka added the
bug
label 1 year ago
Poster
Owner

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

> The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release. > > If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.
gytisrepecka added this to the v0.1.0 milestone 7 months ago
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.