[cordova-coho] branch janpio-CB-13828 updated: add repository setup and order steps of release branch stuff

[ja...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

janpio pushed a commit to branch janpio-CB-13828
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git


The following commit(s) were added to refs/heads/janpio-CB-13828 by this push:
     new f2e92b0  add repository setup and order steps of release branch stuff
f2e92b0 is described below

commit f2e92b0df0fc2a88dbb57ed8d1c78e4cd1683e2c
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Mon Feb 19 19:39:14 2018 +0100

    add repository setup and order steps of release branch stuff
---
 docs/platforms-release-process.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index 3922ee7..fb3c9ba 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -26,6 +26,7 @@ This page describes the technical steps for doing a `Platforms Release`.
 It describes the following steps:
     
 - [General instructions](#general-instructions)
+  * [Repository setup](#repository-setup)
 - [Get Buy-in](#get-buy-in)
 - [Create JIRA issue](#create-jira-issue)
 - [Update and Pin Dependencies](#update-and-pin-dependencies)
@@ -67,7 +68,12 @@ It describes the following steps:
 
 - See: [versioning-and-release-strategy.md](versioning-and-release-strategy.md) for general versioning information
 - Before cutting any releases, read the Apache's [Releases Policy](http://www.apache.org/dev/release)
-- Replace `Android` with the platform you are releasing.
+- Replace `Android` with the platform you are releasing in the instructions below.
+
+### Repository setup
+
+You should have your platform repository checked out in a folder where you als ohave checked out all/most/some of the other Cordova repositories. If you followed the [Cloning/Updating Cordova repositories
+](../README.md#cloningupdating-cordova-repositories) instructions of `cordova-coho`, this should already be the case.
 
 ## Get Buy-in
 
@@ -182,9 +188,9 @@ If you are releasing new commits from an already-existing release branch, rememb
 
 Create and prepare your release branch by using `coho prepare-release-branch` command, which handles the following steps:
 
- * Updating `cordova.js` snapshot
- * Creating a release branch (if it doesn't already exist)
- * Updating version numbers (`VERSION` file & package.json). On `master`, it gives version a minor bump and adds `-dev`
+1. Creating a release branch (if it doesn't already exist)
+2. Updating `cordova.js` snapshot
+3. Updating version numbers (`VERSION` file & package.json). On `master`, it gives version a minor bump and adds `-dev`
 
 Run the following command (make sure to replace the version below with what is listed inside `package.json`).
 

-- 
To stop receiving notification emails like this one, please contact
janpio@apache.org.

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org