remove section on semver, as electron does not fit its mold

This commit is contained in:
Zeke Sikelianos 2017-08-23 13:57:28 -07:00
parent cc80930e2b
commit fe7c827e30

View file

@ -2,34 +2,9 @@
If you've been using Node and npm for a while, you are probably aware of [Semantic Versioning], or SemVer for short. It's a convention for specifying version numbers for software that helps communicate intentions to the users of your software. If you've been using Node and npm for a while, you are probably aware of [Semantic Versioning], or SemVer for short. It's a convention for specifying version numbers for software that helps communicate intentions to the users of your software.
## Overview of Semantic Versioning
Semantic versions are always made up of (at least) three numbers:
```
major.minor.patch
```
Semantic version numbers are bumped (incremented) using the following rules:
* **Major** is for changes that break backwards compatibility.
* **Minor** is for new features that don't break backwards compatibility.
* **Patch** is for bug fixes and other minor changes.
A simple mnemonic for remembering this scheme is as follows:
```
breaking.feature.fix
```
Unstable versions may also have a _pre-release identifier_. See
[Prereleases](#prereleases).
## Electron Versioning
Due to its dependency on Node and Chromium, it is not possible for the Electron Due to its dependency on Node and Chromium, it is not possible for the Electron
project to adhere to a strict SemVer policy. **You should therefore always project to adhere to a strict [Semantic Versioning] policy. **You should
reference a specific version of Electron.** therefore always reference a specific version of Electron.**
Electron version numbers are bumped using the following rules: Electron version numbers are bumped using the following rules: