You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@orc.apache.org by pr...@apache.org on 2017/10/17 07:17:34 UTC
orc git commit: minor updates to make-release doc
Repository: orc
Updated Branches:
refs/heads/master fca456faf -> d2b77247d
minor updates to make-release doc
Project: http://git-wip-us.apache.org/repos/asf/orc/repo
Commit: http://git-wip-us.apache.org/repos/asf/orc/commit/d2b77247
Tree: http://git-wip-us.apache.org/repos/asf/orc/tree/d2b77247
Diff: http://git-wip-us.apache.org/repos/asf/orc/diff/d2b77247
Branch: refs/heads/master
Commit: d2b77247d568958f481ad3cd0cb35d1eb3204b90
Parents: fca456f
Author: Prasanth Jayachandran <pr...@apache.org>
Authored: Tue Oct 17 00:16:06 2017 -0700
Committer: Prasanth Jayachandran <pr...@apache.org>
Committed: Tue Oct 17 00:16:06 2017 -0700
----------------------------------------------------------------------
site/develop/index.md | 6 +++---
site/develop/make-release.md | 19 +++++++++++++------
2 files changed, 16 insertions(+), 9 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/orc/blob/d2b77247/site/develop/index.md
----------------------------------------------------------------------
diff --git a/site/develop/index.md b/site/develop/index.md
index 35aa63f..1f995c2 100644
--- a/site/develop/index.md
+++ b/site/develop/index.md
@@ -5,7 +5,7 @@ title: Developing
Information about the ORC project that is most important for
developers working on the project. The project has created
-[bylaws](bylaws.html) for itself.
+[bylaws](/develop/bylaws) for itself.
## Project Members
@@ -90,7 +90,7 @@ The important branches are:
* [asf-site](https://github.com/apache/orc/tree/asf-site) -
The pages that are deployed to https://orc.apache.org/
-Please check our [coding guidelines](/develop/coding.html).
+Please check our [coding guidelines](/develop/coding).
## Reviews
@@ -99,4 +99,4 @@ committer's review. However, most changes should be reviewed first.
## Making a Release
-The process to make a release is documented [here](/develop/make-release.html).
+The process to make a release is documented [here](/develop/make-release).
http://git-wip-us.apache.org/repos/asf/orc/blob/d2b77247/site/develop/make-release.md
----------------------------------------------------------------------
diff --git a/site/develop/make-release.md b/site/develop/make-release.md
index 6f7354b..379e905 100644
--- a/site/develop/make-release.md
+++ b/site/develop/make-release.md
@@ -45,7 +45,10 @@ sftp> put orc-X.Y.Zrc0*
sftp> quit
~~~
-Make sure your GPG exists in https://dist.apache.org/repos/dist/release/orc/KEYS for others to verify signature in RC
+Make sure your GPG key exists [here](https://dist.apache.org/repos/dist/release/orc/KEYS) for others to verify signature in RC
+
+Click the version to release (X.Y.Z) [here](https://issues.apache.org/jira/projects/ORC?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page)
+to get the list of jiras that are fixed in X.Y.Z
Send email with the vote:
@@ -96,11 +99,15 @@ In a svn clone of https://dist.apache.org/repos/dist/release/orc
% cd orc-X.Y.Z
copy release artifacts with a rename from orc-X.Y.Zrc0* to orc-X.Y.Z*
% svn add .
-% svn commit
-~~~
+% svn commit ---username <apacheid> -m "ORC X.Y.Z Release"
We keep the latest patch release for each of the last two branches, so remove
-extra releases from the Apache dist area.
+extra releases (say I.J.K) from the Apache dist area.
+
+% cd ..
+% svn rm orc-I.J.K
+% svn commit --username <apacheid> -m "Removed old release ORC I.J.K"
+~~~
Update the release branch with the version for the next release.
@@ -123,9 +130,9 @@ Update the site with the new release.
* archived = removed from dist
* create a new file _posts/YYYY-MM-DD-ORC-X.Y.Z.md for the news section
* Run "bundle exec jekyll serve"
-* Check the website on http:/0.0.0.0:4000/
+* Check the website on http://0.0.0.0:4000/
* If it looks good, use git add to add the new files and commit to master with a message of "update site for X.Y.Z".
-* Change directory into target.
+* Change directory into target for publishing the site.
* Add the new files that you just generated.
* This assumes you've set up site/target to be a separate git workspace that tracks the asf-site branch.
* Commit to asf-site to publish the updated site.