You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by ag...@apache.org on 2014/05/01 19:16:05 UTC
git commit: First draft of voting guidelines for releases.
Repository: cordova-coho
Updated Branches:
refs/heads/master 917aeb63b -> 4bff44f86
First draft of voting guidelines for releases.
Project: http://git-wip-us.apache.org/repos/asf/cordova-coho/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-coho/commit/4bff44f8
Tree: http://git-wip-us.apache.org/repos/asf/cordova-coho/tree/4bff44f8
Diff: http://git-wip-us.apache.org/repos/asf/cordova-coho/diff/4bff44f8
Branch: refs/heads/master
Commit: 4bff44f86f0de7b99a98058ad25cb50f692bb23a
Parents: 917aeb6
Author: Andrew Grieve <ag...@chromium.org>
Authored: Thu May 1 13:15:36 2014 -0400
Committer: Andrew Grieve <ag...@chromium.org>
Committed: Thu May 1 13:16:01 2014 -0400
----------------------------------------------------------------------
docs/plugins-release-process.md | 7 ++++-
docs/release-voting.md | 53 ++++++++++++++++++++++++++++++++++++
docs/tools-release-process.md | 7 ++++-
3 files changed, 65 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/4bff44f8/docs/plugins-release-process.md
----------------------------------------------------------------------
diff --git a/docs/plugins-release-process.md b/docs/plugins-release-process.md
index bd8d4f6..6de5758 100644
--- a/docs/plugins-release-process.md
+++ b/docs/plugins-release-process.md
@@ -161,9 +161,14 @@ __Body:__
Upon a successful vote I will upload the archives to dist/, upload them to the Plugins Registry, and post the corresponding blog post.
+ Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
+
Voting will go on for a minimum of 48 hours.
- I vote +1.
+ I vote +1:
+ * Ran coho audit-license-headers over the relevant repos
+ * Used `license-checker` to ensure all dependencies have Apache-compatible licenses
+ * Ensured continuous build was green when repos were tagged
## Email the result of the vote
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/4bff44f8/docs/release-voting.md
----------------------------------------------------------------------
diff --git a/docs/release-voting.md b/docs/release-voting.md
new file mode 100644
index 0000000..b3f2cb9
--- /dev/null
+++ b/docs/release-voting.md
@@ -0,0 +1,53 @@
+# Release Voting Guidelines
+
+Reference: https://www.apache.org/dev/release-publishing.html
+
+Apache releases require at least 3 +1 votes, and there must be more +1s than -1s.
+
+**Note**: There is no benefit in having more than 3 +1 votes. Don't waste your time if a vote already looks in good shape.
+
+How to start / close a vote thread is described in the release process docs.
+This page focuses on what it means to +1 a vote thread.
+
+When we (or at least, members of the PMC), vote on a release, we
+are expressing confidence that:
+1. Our sources are properly licenses*
+2. We have only compatibly licensed dependencies (and appropriate NOTICE lines)*
+3. No IP was added without the concent of its owner**
+4. Archives are properly signed & hashed
+5. Repo tags match sha1 stated in vote email
+6. We believe the quality of the release is better than the previous one
+
+_* These items are generally checked by the Release Manager.
+The Release Manager should state that they've checked them when they +1 the vote._
+
+_** It is the responsibility of committers to ensure that no
+invalid IP enters the codebase. It's not something that we need to re-check
+at each release. For more info, see [this discussion](http://markmail.org/thread/7gqwzrdie46f4qtx)_
+
+When you +1 a vote. You should say what work you did in order to gain confidence in the release.
+
+For example, the Release Manager would say:
+
+ +1
+
+ * Ran coho audit-license-headers over the relevant repos
+ * Used `license-checker` to ensure all dependencies have Apache-compatible licenses
+ * Ensured continuous build was green when repos were tagged
+
+For example, someone else might say:
+
+ +1
+
+ * Confirmed sigs & hashes with `coho verify-archive`
+ * Verified sha1s match tags
+ * Re-created archives to ensure contents match release candidate
+
+About #6 (quality of the release):
+ - We strive to maintain release-worth quality at all times
+ - cordova-medic runs automated tests for each commit
+
+Given these:
+ - Manual testing can be done with release candidates, but is not strictly necessary
+ - Bugs don't block releases, but regressions generally do
+
http://git-wip-us.apache.org/repos/asf/cordova-coho/blob/4bff44f8/docs/tools-release-process.md
----------------------------------------------------------------------
diff --git a/docs/tools-release-process.md b/docs/tools-release-process.md
index 837db7d..ad90b7e 100644
--- a/docs/tools-release-process.md
+++ b/docs/tools-release-process.md
@@ -164,9 +164,14 @@ __Body:__
Upon a successful vote I will upload the archives to dist/, publish them to NPM, and post the corresponding blog post.
+ Voting guidelines: https://github.com/apache/cordova-coho/blob/master/docs/release-voting.md
+
Voting will go on for a minimum of 48 hours.
- I vote +1.
+ I vote +1:
+ * Ran coho audit-license-headers over the relevant repos
+ * Used `license-checker` to ensure all dependencies have Apache-compatible licenses
+ * Ensured continuous build was green when repos were tagged
## Email the result of the vote