You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ja...@apache.org on 2019/05/23 17:18:59 UTC
[cordova-coho] branch janpio-platform_release_jira updated (8782703
-> b1626e6)
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a change to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git.
omit 8782703 remove wrong info
omit f984a16 fix
omit e396838 readd $RELEASE
omit 65e4354 release identifier
omit a0be566 fix
omit ab6e4a5 fix toc
omit d69e922 rest
omit 67b7575 fix up to "Prepare Release"
omit 41dcbe4 replace more JIRA
omit 9e5e6b7 remove JIRA
add 8637279 clarify
add b5ab1ac Clarify working directory (-g etc) (#237)
add 6481e7d Add Node.js 12 to CI Services (#232)
add 799f721 cordova-common singleton rule N/A since Cordova 9 (#224)
add e838cc0 Improvements to src/main.js (#221)
add c92b8a5 fix master (eslint)
new 87ce697 remove JIRA
new 459b94f replace more JIRA
new 5e1e5f2 fix up to "Prepare Release"
new 87c5a1e rest
new 948517e fix toc
new a626e02 fix
new a8a0729 release identifier
new 19168d9 readd $RELEASE
new b1626e6 fix
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (8782703)
\
N -- N -- N refs/heads/janpio-platform_release_jira (b1626e6)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 9 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.travis.yml | 11 ++---
README.md | 2 +-
appveyor.yml | 11 +++--
docs/platforms-release-process.md | 4 +-
docs/setting-up-gpg.md | 28 ++++++++-----
docs/tools-release-process.md | 2 +
src/apputil.js | 2 +-
test/test.js => src/check-npm-install-util.js | 16 ++++----
coho => src/lazy-require-util.js | 17 ++++----
src/main.js | 59 +++++++++++++--------------
10 files changed, 82 insertions(+), 70 deletions(-)
copy test/test.js => src/check-npm-install-util.js (69%)
copy coho => src/lazy-require-util.js (72%)
mode change 100755 => 100644
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 06/09: fix
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit a626e021ce73221beedd2ee8a5bcb9cd047f279f
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Thu May 9 15:12:01 2019 +0200
fix
---
docs/platforms-release-process.md | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index a42d151..ba34362 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -21,21 +21,20 @@
# Release Process for Cordova Platforms
-This page describes the technical steps for doing a `Platforms Release`.
+This page describes the technical steps for doing a Platforms Release.
## Table of contents
-It describes the following steps:
-
- [General instructions](#general-instructions)
* [Read first](#read-first)
* [Repository setup](#repository-setup)
- [Before you start](#before-you-start)
* [Request buy-in](#request-buy-in)
- [Before Release](#before-release)
- * [npm audit check](#npm-audit-check)
+ * [Make sure you're up-to-date](#make-sure-youre-up-to-date)
* [Check dependencies](#check-dependencies)
- [Resolve any outdated dependencies](#resolve-any-outdated-dependencies)
+ * [`npm audit` check](#npm-audit-check)
* [License Check](#license-check)
- [Prepare Release](#prepare-release)
* [Optional: Set release version in `package.json`](#optional-set-release-version-in-packagejson)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 04/09: rest
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 87c5a1e01b9ccfa0b9d371a6ba667798eba550d9
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Wed May 8 22:25:08 2019 +0200
rest
---
docs/platforms-release-process.md | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index c0c8f89..f97af78 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -31,7 +31,6 @@ It describes the following steps:
* [Read first](#read-first)
* [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)
@@ -55,7 +54,7 @@ It describes the following steps:
* [4) `cordova-lib` tests](#4-cordova-lib-tests)
* [5) Clean up](#5-clean-up)
* [When a regression is found](#when-a-regression-is-found)
- * [To submit a fix](#to-submit-a-fix)
+ - [To submit a fix](#to-submit-a-fix)
- [Push Changes](#push-changes)
* [Push commits](#push-commits)
* [Tag and push tag](#tag-and-push-tag)
@@ -67,7 +66,7 @@ It describes the following steps:
* [Start VOTE Thread](#start-vote-thread)
* [Email the result of the vote](#email-the-result-of-the-vote)
* [If the Vote does *not* Pass](#if-the-vote-does-not-pass)
- * [Otherwise: Publish real release to `dist/` & npm](#otherwise-publish-real-release-to-dist--npm)
+ * [Otherwise: Publish release to `dist/` & npm](#otherwise-publish-release-to-dist--npm)
* [(Android only) Uploading to Bintray](#android-only-uploading-to-bintray)
* [Add permanent Apache release tag to repository](#add-permanent-apache-release-tag-to-repository)
- [Follow up steps](#follow-up-steps)
@@ -193,6 +192,7 @@ Update the repos `RELEASENOTES.md` file with changes since the last release.
coho update-release-notes -r android
(`--from-tag` and/or `--to-tag` may be needed in case of non-master branch)
+TODO what does that mean? Examples.
Then curate:
@@ -228,7 +228,7 @@ Create and prepare your release branch by using `coho prepare-platform-release-b
1. Creates a release branch `5.0.x` (if it doesn't already exist)
2. Updates `cordova.js` snapshot on both `5.0.x` and `master`
3. Propagates version number from `--version` argument (or from `package.json` if there is no `--version` argument) to all other files (`VERSION` and similar [e.g. `build.gradle` for Android]) on the release branch `5.0.x`
-4. Prepares `master` for future development already: It gives version (`package.json`, `VERSION` and similar) a minor bump and adds `-dev` (=> `5.1.0-dev`) again
+4. Prepares `master` for future development already: It gives version (`package.json`, `VERSION` and similar) a minor bump and adds `-dev` (=> `5.1.0-dev`) back
Run the following command (make sure to replace the version below with what is listed inside `package.json`).
@@ -306,7 +306,7 @@ rm -rf androidTest*
Create an issue for it and fix it via a Pull Request before continuing.
-### To submit a fix
+#### To submit a fix
git checkout master
git commit -am 'Your commit message'
@@ -396,10 +396,8 @@ __Body:__
Please review and vote on this 5.0.0 Android Release
by replying to this email (and keep discussion on the DISCUSS thread)
- Release issue: https://issues.apache.org/jira/browse/CB-XXXX
-
The archive has been published to dist/dev:
- https://dist.apache.org/repos/dist/dev/cordova/CB-XXXX
+ https://dist.apache.org/repos/dist/dev/cordova/XXX/
The package was published from its corresponding git tag:
### PASTE OUTPUT OF: coho print-tags -r android --tag 5.0.0 ###
@@ -451,13 +449,14 @@ _Note: list of PMC members: http://people.apache.org/phonebook.html?pmc=cordova_
### If the Vote does *not* Pass
-* Revert adding of `-dev`
-* Address the concerns
+* Revert adding of `-dev` on master branch
+* Address the concerns (on master branch)
* Re-tag release using `git tag -f`
+TODO this seems to be missing a few steps here
* Add back `-dev`
* Start a new vote
-### Otherwise: Publish real release to `dist/` & npm
+### Otherwise: Publish release to `dist/` & npm
First move the release package files to `dist/`:
@@ -480,7 +479,7 @@ Then you can also remove the release candidate from `dist-dev/`:
svn commit -m "Removing release candidates from dist/dev"
cd ..
-And finally you can publish your package to `npm`:
+And finally you can publish your package to npm:
cd cordova-dist
npm publish platforms/cordova-android-5.0.0.tgz
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 05/09: fix toc
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 948517e89bc15ab42de25ac9cebccbb1e2fd21b1
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Thu May 9 11:19:09 2019 +0200
fix toc
---
docs/platforms-release-process.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index f97af78..a42d151 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -35,7 +35,7 @@ It describes the following steps:
- [Before Release](#before-release)
* [npm audit check](#npm-audit-check)
* [Check dependencies](#check-dependencies)
- * [Resolve any outdated dependencies](#resolve-any-outdated-dependencies)
+ - [Resolve any outdated dependencies](#resolve-any-outdated-dependencies)
* [License Check](#license-check)
- [Prepare Release](#prepare-release)
* [Optional: Set release version in `package.json`](#optional-set-release-version-in-packagejson)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 09/09: fix
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit b1626e6462e0a0b57329b86914be9b191c5756fc
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Thu May 23 19:06:44 2019 +0200
fix
---
docs/platforms-release-process.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index ab23134..6ed5ef3 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -102,7 +102,7 @@ You should have your platform repository checked out in a folder where you also
Releases are identified by a "Release Identifier" that is used in commit messages and for temporary folders.
-Good choices are unique and have a direct relation to the release you are about to perform. Examples for valid identifiers would be `android20190506` or `android@503`. You can also create a release issue and use that (including the repository name): `cordova-androidn#123`.
+Good choices are unique and have a direct relation to the release you are about to perform. Examples for valid identifiers would be `android20190506` or `android@503`. You can also create a release issue and use that (including the repository name): `cordova-android#123`.
You set it similar to the active plugins:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 08/09: readd $RELEASE
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 19168d92db2bf7c050306a6a003c7417665f4c72
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Thu May 23 18:24:55 2019 +0200
readd $RELEASE
---
docs/platforms-release-process.md | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index 46e9e43..ab23134 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -220,9 +220,9 @@ or use your favorite text editor manually.
Commit these changes together in a single commit (one commit).
- (cd cordova-android && v="$(grep '"version"' package.json | cut -d'"' -f4)" && git commit -am "Update RELEASENOTES & version for release $v")
+ (cd cordova-android && v="$(grep '"version"' package.json | cut -d'"' -f4)" && git commit -am "Update RELEASENOTES & version for release $v ($RELEASE)")
-(Should be `Update RELEASENOTES.md for release $v` in case `version` is not yet updated in `package.json`.)
+(Should be `Update RELEASENOTES.md for release $v ($RELEASE)` in case `version` is not yet updated in `package.json`.)
### Special Case 1: Release notes in release branch for patch release
@@ -370,15 +370,15 @@ Ensure you have the svn repos checked out:
Create archives from your tags:
- coho create-archive -r android --dest cordova-dist-dev --tag 5.0.0
+ coho create-archive -r android --dest cordova-dist-dev/$RELEASE --tag 5.0.0
Sanity Check:
- coho verify-archive cordova-dist-dev/*.tgz
+ coho verify-archive cordova-dist-dev/$RELEASE/*.tgz
Upload:
- (cd cordova-dist-dev && svn add --force . && svn commit -m "Uploading release candidates for android release")
+ (cd cordova-dist-dev && svn add $RELEASE && svn commit -m "Uploading release candidates for android release ($RELEASE)")
If everything went well the Release Candidate will show up here: https://dist.apache.org/repos/dist/dev/cordova/
@@ -481,9 +481,9 @@ First move the release package files to `dist/`:
cd cordova-dist
svn up
svn rm platforms/cordova-android*
- cp ../cordova-dist-dev/cordova-android* platforms/
+ cp ../cordova-dist-dev/$RELEASE/cordova-android* platforms/
svn add platforms/cordova-android*
- svn commit -m "Published android release to dist"
+ svn commit -m "Published android release to dist ($RELEASE)"
Now you can find your release here: https://dist.apache.org/repos/dist/release/cordova/
@@ -491,8 +491,8 @@ Then you can also remove the release candidate from `dist-dev/`:
cd ../cordova-dist-dev
svn up
- svn rm cordova-android*
- svn commit -m "Removing release candidates from dist/dev"
+ svn rm $RELEASE
+ svn commit -m "Removing release candidates from dist/dev ($RELEASE)"
cd ..
And finally you can publish your package to npm:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 03/09: fix up to "Prepare Release"
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 5e1e5f2f71c8ae7603516ae122939ccf9f238aed
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Wed May 8 22:01:55 2019 +0200
fix up to "Prepare Release"
---
docs/platforms-release-process.md | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index 2f796bf..c0c8f89 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -81,7 +81,6 @@ It describes the following steps:
<!-- created with https://ecotrust-canada.github.io/markdown-toc/ and some manual fixing -->
-(Yes this list is long and scary, but represents the content below)
## General instructions
@@ -96,11 +95,8 @@ It describes the following steps:
You should have your platform repository checked out in a folder where you also have 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.
-## Before you start
-
-### Read through Apache release policy
-Read through the [Apache Releases Policy](http://www.apache.org/dev/release) as stated above.
+## Before you start
### Request buy-in
@@ -119,27 +115,24 @@ Double check you replace "Android" in the subject and mail body - there is no un
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
+### Make sure you're up-to-date
-Ensure that the latest version of npm is installed (using a command such as `npm i npm@latest`), `package-lock.json` is present (do `npm i --package-lock-only` if needed), and then check:
+Ensure your checkout of the repository is up-to-date:
- (cd cordova-android && npm audit)
+ coho repo-update -r android # updates the repos
### Check dependencies
-Ensure your checkout of the repository is up-to-date:
-
- coho repo-update -r android
-
See if any dependencies are outdated
(cd cordova-android && npm outdated --depth=0)
(The `--depth=0` prevents from listing dependencies of dependencies.)
-### Resolve any outdated dependencies
+#### Resolve any outdated dependencies
**Alternative 1:**
@@ -150,6 +143,12 @@ See if any dependencies are outdated
Within a new Pull Request: update any outdated dependencies in the project's `package.json` file. Be sure to run through the test section below for compatibility issues.
+### `npm audit` check
+
+Ensure that the latest version of npm is installed (using a command such as `npm i npm@latest`), `package-lock.json` is present (do `npm i --package-lock-only` if needed), and then check:
+
+ (cd cordova-android && npm audit)
+
### License Check
Ensure license headers are present everywhere. For reference, see this [background](http://www.apache.org/legal/src-headers.html). Expect some noise in the output, for example some files from test fixtures will show up.
@@ -160,6 +159,7 @@ Ensure all dependencies and subdependencies have Apache-compatible licenses.
coho check-license -r android
+
## Prepare Release
Preparation of the release includes a) handling version numbers, b) creating nice release notes and c) creating the release branch.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 02/09: replace more JIRA
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 459b94f230455cc0a36ff10b9327a0d5c5c59725
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Mon May 6 15:07:30 2019 +0200
replace more JIRA
---
docs/platforms-release-process.md | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index fe0d409..2f796bf 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -352,19 +352,17 @@ Ensure you have the svn repos checked out:
coho repo-clone -r dist -r dist/dev
-TODO Find replacement for usage of $JIRA here
-
Create archives from your tags:
- coho create-archive -r android --dest cordova-dist-dev/$JIRA --tag 5.0.0
+ coho create-archive -r android --dest cordova-dist-dev --tag 5.0.0
Sanity Check:
- coho verify-archive cordova-dist-dev/$JIRA/*.tgz
+ coho verify-archive cordova-dist-dev/*.tgz
Upload:
- (cd cordova-dist-dev && svn add $JIRA && svn commit -m "$JIRA Uploading release candidates for android release")
+ (cd cordova-dist-dev && svn add --force . && svn commit -m "Uploading release candidates for android release")
If everything went well the Release Candidate will show up here: https://dist.apache.org/repos/dist/dev/cordova/
@@ -468,9 +466,9 @@ First move the release package files to `dist/`:
cd cordova-dist
svn up
svn rm platforms/cordova-android*
- cp ../cordova-dist-dev/$JIRA/cordova-android* platforms/
+ cp ../cordova-dist-dev/cordova-android* platforms/
svn add platforms/cordova-android*
- svn commit -m "$JIRA Published android release to dist"
+ svn commit -m "Published android release to dist"
Now you can find your release here: https://dist.apache.org/repos/dist/release/cordova/
@@ -478,8 +476,8 @@ Then you can also remove the release candidate from `dist-dev/`:
cd ../cordova-dist-dev
svn up
- svn rm $JIRA
- svn commit -m "$JIRA Removing release candidates from dist/dev"
+ svn rm cordova-android*
+ svn commit -m "Removing release candidates from dist/dev"
cd ..
And finally you can publish your package to `npm`:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 07/09: release identifier
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit a8a0729e73687aa094e2eb9571dd14cd0671cba4
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Thu May 23 18:18:22 2019 +0200
release identifier
---
docs/platforms-release-process.md | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index ba34362..46e9e43 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -29,6 +29,7 @@ This page describes the technical steps for doing a Platforms Release.
* [Read first](#read-first)
* [Repository setup](#repository-setup)
- [Before you start](#before-you-start)
+ * [Choose a Release Identifier](#choose-a-release-identifier)
* [Request buy-in](#request-buy-in)
- [Before Release](#before-release)
* [Make sure you're up-to-date](#make-sure-youre-up-to-date)
@@ -96,6 +97,20 @@ You should have your platform repository checked out in a folder where you also
## Before you start
+
+### Choose a Release Identifier
+
+Releases are identified by a "Release Identifier" that is used in commit messages and for temporary folders.
+
+Good choices are unique and have a direct relation to the release you are about to perform. Examples for valid identifiers would be `android20190506` or `android@503`. You can also create a release issue and use that (including the repository name): `cordova-androidn#123`.
+
+You set it similar to the active plugins:
+
+```
+RELEASE=android20190506
+echo $RELEASE
+```
+
### Request buy-in
Email the dev mailing-list at <de...@cordova.apache.org> and see if anyone has reason to postpone the release.
@@ -146,7 +161,9 @@ Within a new Pull Request: update any outdated dependencies in the project's `pa
Ensure that the latest version of npm is installed (using a command such as `npm i npm@latest`), `package-lock.json` is present (do `npm i --package-lock-only` if needed), and then check:
(cd cordova-android && npm audit)
-
+
+TODO Get rid of package-lock.json afterwards
+
### License Check
Ensure license headers are present everywhere. For reference, see this [background](http://www.apache.org/legal/src-headers.html). Expect some noise in the output, for example some files from test fixtures will show up.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org
[cordova-coho] 01/09: remove JIRA
Posted by ja...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
janpio pushed a commit to branch janpio-platform_release_jira
in repository https://gitbox.apache.org/repos/asf/cordova-coho.git
commit 87ce697aa0cad28977f0ff57ada7022d745ca029
Author: Jan Piotrowski <pi...@gmail.com>
AuthorDate: Mon May 6 12:38:30 2019 +0200
remove JIRA
---
docs/platforms-release-process.md | 35 +++++++----------------------------
1 file changed, 7 insertions(+), 28 deletions(-)
diff --git a/docs/platforms-release-process.md b/docs/platforms-release-process.md
index 69abc5d..fe0d409 100644
--- a/docs/platforms-release-process.md
+++ b/docs/platforms-release-process.md
@@ -38,7 +38,6 @@ It describes the following steps:
* [Check dependencies](#check-dependencies)
* [Resolve any outdated dependencies](#resolve-any-outdated-dependencies)
* [License Check](#license-check)
- * [Create JIRA issue](#create-jira-issue)
- [Prepare Release](#prepare-release)
* [Optional: Set release version in `package.json`](#optional-set-release-version-in-packagejson)
- [Remove the `-dev` suffix from version](#remove-the--dev-suffix-from-version)
@@ -75,7 +74,6 @@ It describes the following steps:
* [Tell Apache about Release](#tell-apache-about-release)
* [Email a release announcement to the mailing list](#email-a-release-announcement-to-the-mailing-list)
* [Announce It!](#announce-it)
- * [Close JIRA issue](#close-jira-issue)
* [Finally](#finally)
- [Other stuff that should be reviewed and moved up to the appropriate places](#other-stuff-that-should-be-reviewed-and-moved-up-to-the-appropriate-places)
* [Update the Docs](#update-the-docs)
@@ -146,11 +144,11 @@ See if any dependencies are outdated
**Alternative 1:**
- Explicitly pin the outdated dependency versions in the `dependencies` section of `package.json`.
-- Raise a new JIRA issue to update the dependencies in an upcoming release.
+- Raise a new issue to update the dependencies in an upcoming release.
**Alternative 2:**
-Within a new JIRA issue: update any outdated dependencies in the project's `package.json` file. Be sure to run through the test section below for compatibility issues.
+Within a new Pull Request: update any outdated dependencies in the project's `package.json` file. Be sure to run through the test section below for compatibility issues.
### License Check
@@ -162,22 +160,6 @@ Ensure all dependencies and subdependencies have Apache-compatible licenses.
coho check-license -r android
-### 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_"
- - Description should be: "Following steps at https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md"
- * Comments should be added to this bug after each top-level step below is taken
- * Set a variable in your terminal for use later on
-
-
-```
-JIRA="CB-????" # Set this to the release bug.
-```
-
## Prepare Release
Preparation of the release includes a) handling version numbers, b) creating nice release notes and c) creating the release branch.
@@ -222,9 +204,9 @@ or use your favorite text editor manually.
Commit these changes together in a single commit (one commit).
- (cd cordova-android && v="$(grep '"version"' package.json | cut -d'"' -f4)" && git commit -am "$JIRA Update RELEASENOTES & version for release $v")
+ (cd cordova-android && v="$(grep '"version"' package.json | cut -d'"' -f4)" && git commit -am "Update RELEASENOTES & version for release $v")
-(Should be "$JIRA Update RELEASENOTES.md for release $v" in case `version` is not yet updated in `package.json`.)
+(Should be `Update RELEASENOTES.md for release $v` in case `version` is not yet updated in `package.json`.)
### Special Case 1: Release notes in release branch for patch release
@@ -322,7 +304,7 @@ rm -rf androidTest*
### When a regression is found
-Create a JIRA issue for it, and mark it as a blocker.
+Create an issue for it and fix it via a Pull Request before continuing.
### To submit a fix
@@ -370,6 +352,8 @@ Ensure you have the svn repos checked out:
coho repo-clone -r dist -r dist/dev
+TODO Find replacement for usage of $JIRA here
+
Create archives from your tags:
coho create-archive -r android --dest cordova-dist-dev/$JIRA --tag 5.0.0
@@ -559,11 +543,6 @@ Announce the release to the world!
* Publish the release blog post
* Tweet it on https://twitter.com/apachecordova
-### Close JIRA Issue
-
-- Double check that the issue includes comments that record the steps you took
-- Mark it as fixed
-
### Finally
- Update these instructions if they were missing anything.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org