[GitHub] brodybits closed pull request #183: Clarify platform release buy-in and JIRA issue timing

[GitBox <gi...@apache.org>]

brodybits closed pull request #183: Clarify platform release buy-in and JIRA issue timing
URL: https://github.com/apache/cordova-coho/pull/183
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index 208d503..093cf3a 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -32,12 +32,12 @@ It describes the following steps:
   * [Repository setup](#repository-setup)
 - [Before you start](#before-you-start)
   * [Read through Apache release policy](#read-through-apache-release-policy)
+  * [Request buy-in](#request-buy-in)
 - [Before Release](#before-release)
   * [npm audit check](#npm-audit-check)
   * [Check dependencies](#check-dependencies)
   * [Resolve any outdated dependencies](#resolve-any-outdated-dependencies)
   * [License Check](#license-check)
-  * [Get Buy-in](#get-buy-in)
   * [Create JIRA issue](#create-jira-issue)
 - [Prepare Release](#prepare-release)
   * [Optional: Set release version in `package.json`](#optional-set-release-version-in-packagejson)
@@ -105,6 +105,23 @@ You should have your platform repository checked out in a folder where you also
 
 Read through the [Apache Releases Policy](http://www.apache.org/dev/release) as stated above. 
 
+### Request buy-in
+
+Email the dev mailing-list at <de...@cordova.apache.org> and see if anyone has reason to postpone the release.
+
+E.g.:
+
+    Subject: [DISCUSS] Cordova-Android Release
+
+    Does anyone have any reason to delay a cordova-_android_ platform release?
+    Any outstanding patches to land?
+
+    If not, I will start the release tomorrow.
+
+Double check you replace "Android" in the subject and mail body - there is no undo for emails.
+
+Note that it would be possible to continue with some of the [Before Release](#before-release) items while waiting for a possible response.
+
 ## Before Release
 
 ### npm audit check
@@ -157,23 +174,10 @@ Ensure all dependencies and subdependencies have Apache-compatible licenses.
 
     coho check-license -r android
 
-### Get Buy-in
-
-Email the dev mailing-list at dev@cordova.apache.org and see if anyone has reason to postpone the release.
-
-E.g.:
-
-    Subject: [DISCUSS] Cordova-Android Release
-
-    Does anyone have any reason to delay a cordova-_android_ platform release?
-    Any outstanding patches to land?
-
-    If not, I will start the release tomorrow.
-
-Double check you replace "Android" in the subject and mail body - there is no undo for emails.
-
 ### Create JIRA issue
 
+After waiting for any possible objections from the email sent according to the [Request buy-in](#request-buy-in) section above:
+
  * Create a JIRA issue to track the status of the release.
    - Make it of type "Task"
    - Title should be "Cordova-Android Platform Release _August 21, 2014_"


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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