You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by br...@apache.org on 2018/08/01 01:12:00 UTC

[cordova-coho] branch master updated: Quick tools release planning notes (#185)

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

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


The following commit(s) were added to refs/heads/master by this push:
     new b502887  Quick tools release planning notes (#185)
b502887 is described below

commit b50288707ae68374f34ecf6582b0fd4dc0690eae
Author: Chris Brody <ch...@gmail.com>
AuthorDate: Tue Jul 31 21:11:58 2018 -0400

    Quick tools release planning notes (#185)
---
 docs/tools-release-process.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/tools-release-process.md b/docs/tools-release-process.md
index 3c09f0d..680b205 100644
--- a/docs/tools-release-process.md
+++ b/docs/tools-release-process.md
@@ -32,6 +32,19 @@ A tools release is performed by a single person each week. We call this person t
 ## Decide on the next version numbers
 According [versioning-and-release-strategy.md](versioning-and-release-strategy.md) patch version bumps (the last of 3 numbers) should only be used for fixes and updates of references to platform versions. For any change in functionality, the second (minor) part of the version should be bumped and new branch created. Instructions for creating a new release branch are further down on this page.
 
+## Tools release planning
+
+### cordova-create principle
+
+The most important principle is that packages such as `cordova-lib` and `cordova-cli` should not use multiple versions of `cordova-common` through the chain of dependencies. This means that if `cordova-common` is updated it should be released before other packages such as `cordova-fetch`, `cordova-create`, `cordova-lib`, `cordova-cli`, etc.
+
+### Alternative approaches
+
+This document describes how to release all tools packages at once but this is not the only possible approach. The following alternative approaches are also possible:
+
+ * release a single tools package
+ * release multiple tools packages in sequence, as needed to satisfy 
+
 ## Get Buy-in
 
 Email the dev mailing-list and see if anyone has reason to postpone the release.


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