Repository: incubator-livy-website
Updated Branches:
  refs/heads/master 8e789d14f -> b5bb554b2

[LIVY-434][DOCS] Added Release Process Doc to website

I've rewritten my Release Process Documentation that I wrote during the 0.5 
release into a md Doc for the website.

This doc is hidden (as in not links to it on the site) since it is for release 
managers not users and is a WIP until graduation.

Author: Alex Bozarth <>

Closes #19 from ajbozarth/doc.


Branch: refs/heads/master
Commit: b5bb554b2c5c288f9c51148f193fa296f71d3fc0
Parents: 8e789d1
Author: Alex Bozarth <>
Authored: Tue Feb 13 12:54:41 2018 -0800
Committer: Alex Bozarth <>
Committed: Tue Feb 13 12:54:41 2018 -0800

 site/ | 103 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)
diff --git a/site/ b/site/
new file mode 100644
index 0000000..2005184
--- /dev/null
+++ b/site/
@@ -0,0 +1,103 @@
+layout: page
+title: Livy - Release Process
+tagline: Release Process
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+{% include JB/setup %}
+# Preparing Livy Releases
+*Note: This document is a work in progress and is not guaranteed to be a 
comprehensive release guide*
+## Overview
+The release manger for a Apache Livy release is in charge of:
+1. Cut and update branches and tags
+1. Create and publish release distros and artifacts to staging locations
+1. Call a vote to authorize release
+1. Publish the release (once a vote passes)
+1. After the release is complete
+### Prepare for release
+If this is your first release it may be useful to read some of the following:
+- <a href="";>Apache Software Release 
+- <a href="";>Apache 
Incubator Podling Release Policies</a>
+- <a href="";>Apache Guide on 
Signing Releases</a>
+- <a href="";>The Apache Spark 
Release Guide</a> (for comparison)
+### Cut and update branches and tags
+1. Create new branch (from master if a major/minor version, or branch-X.x for 
a maintenance version for version X.x) then push it to apache.
+1. Update the master branch with to the next version if this is a major/minor 
+1. Remove SNAPSHOT from the version on branch then cut rc1 tag.
+1. After cutting the rc1 tag you can then update the branch with the next 
maintenance version. (Note: If you do this prior to release any changes between 
rc’s will be individually cherry-picked)
+### Create and publish release distros and artifacts to staging locations
+1. Make sure your public key is in the KEY file in the Livy Dist. Directions 
for creating your key for releases can be found
+<a href="";>here</a>.
+1. Publish the release archives to the Apache dev dist for dev testing (these 
will be moved to the release dist after a successful vote).
+    1. Set env variables as described in ``dev/`` (or utilize 
the script's prompts).
+    1. Run ``dev/ package`` (Note: You may need to run 
``GPG_TTY=$(tty); export GPG_TTY`` for the script to work).
+    1. Double check the distros has been uploaded to the <a 
href="";>dev dist</a>.
+1. Use ``dev/ publish-release`` to push the release artifacts 
to the apache staging repo
+(Note: Make sure sha1 is installed before running the script). Double check 
that the artifacts were published successfully by checking the
+<a href="";>staging repo</a>.
+### Call a vote to authorize release
+1. Email the Livy dev mailing list to call for vote on the release candidate 
and make sure to note that if it passes it will go to an official vote on the 
Incubator general mailing list.
+1. If the vote passes email the Incubator general list to call for a PMC vote. 
+If the vote fails, address the issues raised and cut a new rc with the 
required fixes.
+### Publish the release (once a vote passes)
+1. Go to the <a 
href="";>staging repo</a>, 
select the livy repo from the ``publish-release`` step above 
+and click the "release" button at the top of the page to release the new Livy 
version artifacts.
+1. Move the contents of the <a 
href="";>dev dist</a> to 
+<a href="";>release 
dist</a> (removing the rc# from the folder name).
+    1. Example steps
+        ```bash
+       $ svn co
+       $ export SVN_EDITOR=vim
+       $ svn mv
+        ```
+    1. If you updated the KEYS file during this release make sure you also 
copy that as well. 
+1. Checkout the rc git tag and recommit it without the rc# (Example below)
+    ```bash
+   $ git tag -a v0.5.0-incubating -m "Apache Livy 0.5.0-incubating"
+   $ git push --delete apache v0.5.0-incubating-rc1
+    ```
+1. Announce the release to the Incubator general, Livy dev, and Livy user 
mailing lists 
+(<a href="Incubator general, Livy dev and Livy user">Example Email</a>), if 
you want you can complete the website update step below to include links in the 
+### After the release is complete
+1. Open a PR to update the website with the new latest version number, release 
notes, and a copy of the Docs built using the new release.
+1. If there were any non-blocking issues raised during the vote make sure 
there are open JIRAs to address them in the next release.

Reply via email to