brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From drigod...@apache.org
Subject [1/4] brooklyn-docs git commit: Update release notes for release 0.10.0
Date Thu, 19 Jan 2017 11:51:01 GMT
Repository: brooklyn-docs
Updated Branches:
  refs/heads/master c3621e20d -> d2e6a6780


Update release notes for release 0.10.0


Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/1d428f87
Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/1d428f87
Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/1d428f87

Branch: refs/heads/master
Commit: 1d428f87dd4b708a5b0c99421dde29c4870d2c0c
Parents: 84f1fe2
Author: Svetoslav Neykov <svetoslav.neykov@cloudsoftcorp.com>
Authored: Mon Dec 5 14:21:19 2016 +0200
Committer: Svetoslav Neykov <svetoslav.neykov@cloudsoftcorp.com>
Committed: Mon Dec 26 16:05:22 2016 +0200

----------------------------------------------------------------------
 .../committers/release-process/index.md         | 21 ++++----
 .../release-process/prepare-for-release.md      | 12 +++++
 .../committers/release-process/prerequisites.md |  9 ++--
 .../committers/release-process/publish-temp.md  |  4 +-
 .../release-process/release-version.md          |  2 +-
 .../release-process/verify-release-artifacts.md |  2 +-
 .../committers/release-process/vote.md          | 52 +++++++++++++++++++-
 7 files changed, 83 insertions(+), 19 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/index.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/index.md b/website/developers/committers/release-process/index.md
index 812d3f6..782e462 100644
--- a/website/developers/committers/release-process/index.md
+++ b/website/developers/committers/release-process/index.md
@@ -14,14 +14,15 @@ children:
 - { path: publish.md }
 - { path: announce.md }
 ---
-1. [Prerequisites](prerequisites.html) - steps that a new release manager must do (but which
only need to be done once)
-2. [Set environment variables](environment-variables.html) - many example snippets here use
environment variables to
+1. [Preparing for a release](prepare-for-release.html) - How to prepare the project for a
release
+2. [Prerequisites](prerequisites.html) - steps that a new release manager must do (but which
only need to be done once)
+3. [Set environment variables](environment-variables.html) - many example snippets here use
environment variables to
    avoid repetition - this page describes what they are
-2. [Create a release branch and set the version](release-version.html)
-3. [Make the release artifacts](make-release-artifacts.html)
-4. [Verify the release artifacts](verify-release-artifacts.html)
-5. [Publish the release artifacts to the staging area](publish-temp.html)
-6. [Vote on the dev@brooklyn list](vote.html)
-   1. If the vote fails - [fix the release branch](fix-release.html) and resume from step
3
-7. [Publish the release artifacts to the public location](publish.html)
-8. [Announce the release](announce.html)
+4. [Create a release branch and set the version](release-version.html)
+5. [Make the release artifacts](make-release-artifacts.html)
+6. [Verify the release artifacts](verify-release-artifacts.html)
+7. [Publish the release artifacts to the staging area](publish-temp.html)
+8. [Vote on the dev@brooklyn list](vote.html)
+  1. If the vote fails - [fix the release branch](fix-release.html) and resume from step
4
+9. [Publish the release artifacts to the public location](publish.html)
+10. [Announce the release](announce.html)

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/prepare-for-release.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/prepare-for-release.md b/website/developers/committers/release-process/prepare-for-release.md
new file mode 100644
index 0000000..36bbf98
--- /dev/null
+++ b/website/developers/committers/release-process/prepare-for-release.md
@@ -0,0 +1,12 @@
+---
+layout: website-normal
+title: Prepare the project for a release
+navgroup: developers
+---
+
+1. Make sure all unit and integration tests are passing.
+2. Follow the [classic](https://github.com/apache/brooklyn-dist/blob/master/dist/licensing/README.md#update-license-information)
+   and [karaf](https://github.com/apache/brooklyn-dist/pull/63) instructions to
+   update the licenses of source and binary dependencies. 
+3. Update the [release notes](https://github.com/apache/brooklyn-docs/blob/master/guide/misc/release-notes.md).
To help
+   in the process [list merged PRs](https://gist.github.com/sjcorbett/72ed944b06ce3a138fbe516e8d36f624)
after a ceratin date.

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/prerequisites.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/prerequisites.md b/website/developers/committers/release-process/prerequisites.md
index c4269f5..18d825d 100644
--- a/website/developers/committers/release-process/prerequisites.md
+++ b/website/developers/committers/release-process/prerequisites.md
@@ -58,8 +58,9 @@ The release manager must have a GPG key to be used to sign the release.
See belo
 (not using `whoami` if that's not appropriate):
 
 {% highlight bash %}
-GPG_KEY=`whoami`@apache.org
-SVN_USERNAME=`whoami`
+ASF_USERNAME=`whoami`
+GPG_KEY=$ASF_USERNAME@apache.org
+SVN_USERNAME=$ASF_USERNAME
 {% endhighlight %}
 
 If you have an existing GPG key, but it does not include your Apache email address, you can
add your email address as
@@ -78,8 +79,8 @@ Now add your key to the `apache-dist-release-brooklyn/KEYS` file:
 
 {% highlight bash %}
 cd apache-dist-release-brooklyn
-(gpg2 --list-sigs richard@apache.org && gpg2 --armor --export richard@apache.org)
>> KEYS
-svn --username $SVN_USERNAME commit -m 'Update brooklyn/KEYS for $GPG_KEY'
+(gpg2 --list-sigs $ASF_USERNAME@apache.org && gpg2 --armor --export $ASF_USERNAME@apache.org)
>> KEYS
+svn --username $SVN_USERNAME --no-auth-cache commit -m "Update brooklyn/KEYS for $GPG_KEY"
 {% endhighlight %}
 
 References:

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/publish-temp.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/publish-temp.md b/website/developers/committers/release-process/publish-temp.md
index 0a87444..278ce73 100644
--- a/website/developers/committers/release-process/publish-temp.md
+++ b/website/developers/committers/release-process/publish-temp.md
@@ -38,7 +38,7 @@ and all associated `.md5`, `.sha1`, `.sha256` and `.asc` signatures. Then
commit
 
 {% highlight bash %}
 svn add apache-brooklyn-${VERSION_NAME}-rc${RC_NUMBER}
-svn commit --message "Add apache-brooklyn-${VERSION_NAME}-rc${RC_NUMBER} to dist/dev/brooklyn"
+svn commit --username $SVN_USERNAME --no-auth-cache --message "Add apache-brooklyn-${VERSION_NAME}-rc${RC_NUMBER}
to dist/dev/brooklyn"
 {% endhighlight %}
 
 These steps can be performed as part of the `make-release-artifacts.sh` script used earlier
@@ -54,4 +54,4 @@ be used for downloading the artifacts.
 Go to the Apache Nexus server at [https://repository.apache.org/](https://repository.apache.org/)
and log in using the
 link in the top right (the credentials are the same as your Git and Jenkins credentials).
Go to the "Staging
 Repositories" page, and tick the repository with the name starting `orgapachebrooklyn`. Click
the **Close** button.
-Provide a description which includes the version and release candidate, e.g. `Apache Brooklyn
0.7.0-incubating-rc1`.
+Provide a description which includes the version and release candidate, e.g. `Apache Brooklyn
0.10.0-rc1`.

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/release-version.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/release-version.md b/website/developers/committers/release-process/release-version.md
index ac83e77..36bbc40 100644
--- a/website/developers/committers/release-process/release-version.md
+++ b/website/developers/committers/release-process/release-version.md
@@ -44,7 +44,7 @@ git add . && git commit -m "Change version to $VERSION_NAME"
 If you are happy with the changes, push them:
 
 {% highlight bash %}
-for m in $MODULES; do ( cd $m && git push apache-git $VERSION ); done
+for m in $MODULES; do ( cd $m && git push apache-git $VERSION_NAME ); done
 {% endhighlight %}
 
 

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/verify-release-artifacts.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/verify-release-artifacts.md b/website/developers/committers/release-process/verify-release-artifacts.md
index ffc6fd9..6c2d85e 100644
--- a/website/developers/committers/release-process/verify-release-artifacts.md
+++ b/website/developers/committers/release-process/verify-release-artifacts.md
@@ -17,7 +17,7 @@ release. You should determine the following information and set your environment
 
 {% highlight bash %}
 # The version we are releasing now.
-VERSION_NAME=0.9.0
+VERSION_NAME=0.10.0
 
 # The release candidate number we are making now.
 RC_NUMBER=1

http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/1d428f87/website/developers/committers/release-process/vote.md
----------------------------------------------------------------------
diff --git a/website/developers/committers/release-process/vote.md b/website/developers/committers/release-process/vote.md
index 144abe7..8030dee 100644
--- a/website/developers/committers/release-process/vote.md
+++ b/website/developers/committers/release-process/vote.md
@@ -8,7 +8,7 @@ Start the vote
 --------------
 
 A script to generate the voting email can be found in `brooklyn-dist/release/print-vote-email.sh`,
-taking a single argument being the staging repo link. For example:
+taking a single argument being the staging repo ID. For example:
 
     brooklyn-dist/release/print-vote-email.sh orgapachebrooklyn-1234 | pbcopy
 
@@ -67,6 +67,56 @@ Thanks,
 [Release manager name]
 {% endhighlight %}
 
+Discuss the vote
+----------------
+Open a parallel thread for a place to discuss the vote. Name it [DISCUSS]<Subject of the
voting email>, replying
+to the vote email. Here's an example body for the email.
+
+{% highlight text %}
+This thread is for discussions related to the release vote.
+
+I should clarify what we are looking for in a release vote. Particularly,
+we are looking for people to download,validate, and test the release.
+Only if you are satisfied that the artifacts are correct and the quality is
+high enough, should you make a "+1" vote. Alongside your vote you should list
+the checks that you made.
+
+Here is a good example: http://markmail.org/message/gevsz2pdciraw6jw
+
+The vote is not simply about "the master branch contains the features I wanted" -
+it is about making sure that *these* artifacts are *correct* (e.g. they are
+not corrupted, hashes and signatures pass) and are of *sufficiently high
+quality* to be stamped as an official release of The Apache Software Foundation.
+
+Why test the artifacts when master is looking good? Here are some reasons:
+
+- somebody could have made a commit that broke it, since you last git pulled
+- the release branch could have been made at the wrong point, or inconsistently
+  between all of the submodules
+- something in the release process could have broken it
+- I could have made a mistake and corrupted the files
+- a problem with the Apache infrastructure could mean that the release files are
+  unobtainable or corrupted
+
+This is why the release manager needs you to download the actual release
+artifacts and try them out.
+
+The way Apache works can be a bit arcane sometimes, but it's all done with
+a reason. If the vote passes then the contents of the email and its links
+become "endorsed" by The Apache Software Foundation, and the Foundation will
+take on legal liability for them, forever.
+
+And of course we want the best possible experience for our users - so we need
+the actual release files to be tested manually to make sure that a mistake does
+not ruin the experience for users.
+
+So if you can spare an hour or more to download some of the artifacts and try
+them out, then it will be *very* useful! The vote lasts for three days so
+there's no need to rush to get a vote in.
+
+Thanks!
+[Release manager name]
+{% endhighlight %}
 
 Reply to vote
 -------------


Mime
View raw message