From b2096205149f707f93d599e262664f83e16ea860 Mon Sep 17 00:00:00 2001 From: Charles Kerr Date: Mon, 4 Dec 2017 09:51:12 -0600 Subject: [PATCH] trim whitespace --- docs/development/releasing.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/development/releasing.md b/docs/development/releasing.md index c48fc0dd5e23..db5b93180c72 100644 --- a/docs/development/releasing.md +++ b/docs/development/releasing.md @@ -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