mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

trim whitespace

Browse source
This commit is contained in:
Charles Kerr 2017-12-04 09:51:12 -06:00
parent e5f4916e31
commit b209620514
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/development/releasing.md
View file

@ -10,7 +10,7 @@ This document describes the process for releasing a new version of Electron.
## Find out what version change is needed
Run `npm run prepare-release -- --notesOnly` to view auto generated release
notes. The notes generated should help you determine if this is a major,
notes. The notes generated should help you determine if this is a major,
minor, patch, or beta version change. Read the
[Version Change Rules](../tutorial/electron-versioning.md#version-change-rules)
for more information.
@ -19,7 +19,7 @@ for more information.
The prepare release script will do the following:
1. Check if a release is already in process and if so it will halt.
2. Create a release branch.
3. Bump the version number in several files. See [this bump commit] for an
3. Bump the version number in several files. See [this bump commit] for an
example.
4. Create a draft release on GitHub with auto-generated release notes
5. Push the release branch so that the release builds get built.
@ -198,7 +198,7 @@ npm run merge-release -- 1-7-x
## Publish the release
Once the merge has finished successfully, run the `release` script
via `npm run release` to finish the release process. This script will do the
via `npm run release` to finish the release process. This script will do the
following:
1. Build the project to validate that the correct version number is being released.
2. Download the binaries and generate the node headers and the .lib linker used