Author: stoty
Date: Thu Jan 28 08:00:32 2021
New Revision: 1885967
URL: http://svn.apache.org/viewvc?rev=1885967&view=rev
Log:
PHOENIX-6315 Update website for the new create_release script and process
Modified:
phoenix/site/publish/language/datatypes.html
phoenix/site/publish/language/functions.html
phoenix/site/publish/language/index.html
phoenix/site/publish/release.html
phoenix/site/source/src/site/markdown/release.md
Modified: phoenix/site/publish/language/datatypes.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/language/datatypes.html?rev=1885967&r1=1885966&r2=1885967&view=diff
==============================================================================
--- phoenix/site/publish/language/datatypes.html (original)
+++ phoenix/site/publish/language/datatypes.html Thu Jan 28 08:00:32 2021
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2020-12-31
+ Generated by Apache Maven Doxia at 2021-01-13
Rendered using Reflow Maven Skin 1.1.0
(http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -990,7 +990,7 @@ syntax-end -->
<div class="row">
<div class="span12">
<p class="pull-right"><a href="#">Back to
top</a></p>
- <p class="copyright">Copyright ©2020 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
+ <p class="copyright">Copyright ©2021 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
</div>
</div>
</div>
Modified: phoenix/site/publish/language/functions.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/language/functions.html?rev=1885967&r1=1885966&r2=1885967&view=diff
==============================================================================
--- phoenix/site/publish/language/functions.html (original)
+++ phoenix/site/publish/language/functions.html Thu Jan 28 08:00:32 2021
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2020-12-31
+ Generated by Apache Maven Doxia at 2021-01-13
Rendered using Reflow Maven Skin 1.1.0
(http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -2297,7 +2297,7 @@ syntax-end -->
<div class="row">
<div class="span12">
<p class="pull-right"><a href="#">Back to
top</a></p>
- <p class="copyright">Copyright ©2020 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
+ <p class="copyright">Copyright ©2021 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
</div>
</div>
</div>
Modified: phoenix/site/publish/language/index.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/language/index.html?rev=1885967&r1=1885966&r2=1885967&view=diff
==============================================================================
--- phoenix/site/publish/language/index.html (original)
+++ phoenix/site/publish/language/index.html Thu Jan 28 08:00:32 2021
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2020-12-31
+ Generated by Apache Maven Doxia at 2021-01-13
Rendered using Reflow Maven Skin 1.1.0
(http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -2089,7 +2089,7 @@ syntax-end -->
<div class="row">
<div class="span12">
<p class="pull-right"><a href="#">Back to
top</a></p>
- <p class="copyright">Copyright ©2020 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
+ <p class="copyright">Copyright ©2021 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
</div>
</div>
</div>
Modified: phoenix/site/publish/release.html
URL:
http://svn.apache.org/viewvc/phoenix/site/publish/release.html?rev=1885967&r1=1885966&r2=1885967&view=diff
==============================================================================
--- phoenix/site/publish/release.html (original)
+++ phoenix/site/publish/release.html Thu Jan 28 08:00:32 2021
@@ -1,7 +1,7 @@
<!DOCTYPE html>
<!--
- Generated by Apache Maven Doxia at 2020-12-31
+ Generated by Apache Maven Doxia at 2021-01-13
Rendered using Reflow Maven Skin 1.1.0
(http://andriusvelykis.github.io/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
@@ -168,34 +168,81 @@
<div class="page-header">
<h1>How to do a release</h1>
</div>
-<p>Following instructions walks you through releasing
Phoenix-4.15.0-HBase-1.3. These steps needs to be repeated for all HBase
branches.</p>
+<p>Phoenix has several repos, phoenix-thirdparty, phoenix-omid,
phoenix-tephra, phoenix, phoenix-connectors and phoenix-queryserver The
create-release scripts provide a unified script to handle the release from each
repo. The create-release scripts are in the master branch phoenix repo, in the
dev/create-release directory.</p>
<div class="section">
<h2 id="Pre-Reqs">Pre-Reqs</h2>
<ol style="list-style-type: decimal">
- <li>Make sure you have setup your user for release signing. Details <a
class="externalLink"
href="http://www.apache.org/dev/release-signing.html";>http://www.apache.org/dev/release-signing.html</a>.</li>
- <li>Clone the branch locally from which you want to do a release.</li>
- <li> <p>Set version to release and commit.</p>
- <div>
- <pre>
-mvn versions:set -DnewVersion=4.15.0-HBase-1.3 -DgenerateBackupPoms=false
-</pre>
- </div></li>
+ <li>Make sure that the JIRAs included in the release have their fix-version
and release notes fields set correctly, and are resolved. The script will query
them, and create the CHANGES and RELEASE_NOTES files from that
information.</li>
+ <li>Make sure you have set up your user for release signing. Details <a
class="externalLink"
href="http://www.apache.org/dev/release-signing.html";>http://www.apache.org/dev/release-signing.html</a>.</li>
+ <li>Make sure you have set up maven for deploying to the ASF repo. Details
<a class="externalLink"
href="https://infra.apache.org/publishing-maven-artifacts.html";>https://infra.apache.org/publishing-maven-artifacts.html</a></li>
+ <li>Clone the phoenix master branch locally (the script will download the
actual repo to release itself)</li>
+ <li>Make sure docker is running locally</li>
</ol>
+ <p>Note that Docker Desktop for Mac works, but will be slow. (Several hours
for for a phoenix (core) release ). Running on a native Linux machine is much
faster, as you do not incur the filesystem translation layer penalty</p>
</div>
<div class="section">
- <h2 id="Build_binary_and_source_tars">Build binary and source tars</h2>
- <div>
- <pre>
-$ cd dev; ./make_rc.sh
+ <h2 id="Do_a_dry_run">Do a dry run</h2>
+ <p>Read /dev/create_release/README.txt to get an idea of what the script
does, and how to set up gpg-agent for signing.</p>
+ <p>Run the <tt>dev/create-release/do-release-docker.sh -d <workdir> -p
<project></tt> command, where</p>
+ <ul>
+ <li><tt><project></tt> is the repo name youâre releasing from (i.e.
phoenix)</li>
+ <li><tt><workdir></tt> is any existing directory that can be
deleted</li>
+ </ul>
+ <p>The script will ask a number of questions. Some of them will have
intelligent default, but make sure you check them all:</p>
+ <div class="source">
+ <pre> [stoty@IstvanToth-MBP15:~/workspaces/apache-phoenix/phoenix
(PHOENIX-6307)$]dev/create-release/do-release-docker.sh -p phoenix -d
~/x/phoenix-build/
+ Output directory already exists. Overwrite and continue? [y/n] y
+ ========================
+ === Gathering release details.
+
+ PROJECT [phoenix]:
+ GIT_BRANCH []: master
+ Current branch VERSION is 5.1.0-SNAPSHOT.
+ RELEASE_VERSION [5.1.0]:
+ RC_COUNT [0]:
+ RELEASE_TAG [5.1.0RC0]:
+ This is a dry run. If tag does not actually exist, please confirm the ref
that will be built for testing.
+ GIT_REF [5.1.0RC0]:
+ ASF_USERNAME [stoty]:
+ GIT_NAME [Istvan Toth]:
+ GPG_KEY [st...@apache.org]:
+ We think the key 'st...@apache.org' corresponds to the key id '0x77E592D4'.
Is this correct [y/n]? y
+ ================
+ Release details:
+ GIT_BRANCH: master
+ RELEASE_VERSION: 5.1.0
+ RELEASE_TAG: 5.1.0RC0
+ API_DIFF_TAG:
+ ASF_USERNAME: stoty
+ GPG_KEY: 0x77E592D4
+ GIT_NAME: Istvan Toth
+ GIT_EMAIL: st...@apache.org
+ DRY_RUN: yes
+ ================
</pre>
</div>
- <p>Follow the instructions. Signed binary and source tars will be generated
in the <i>release</i> directory. As last part of this script, it will ask if
you want to tag the branch at this time (sample tag:
<tt>v4.15.0-HBase-1.3-rc0</tt>). If all looks good then svn commit binary and
source tars to <a class="externalLink"
href="https://dist.apache.org/repos/dist/dev/phoenix";>https://dist.apache.org/repos/dist/dev/phoenix</a>
</p>
+ <ul>
+ <li>PROJECT: the repo to release (default specified by -p on the command
line)</li>
+ <li>GIT_BRANCH: the git branch to use for release. This can be master, or a
pre-created release branch.</li>
+ <li>RC_COUNT: the RC number, starting from 0</li>
+ <li>RELEASE_TAG: the git tag the the script will tag the RC commit
with.</li>
+ <li>ASF_USERNAME: your ASF username, for publishing the release
artifacts.</li>
+ <li>ASF_PASSOWORD: your ASF password, only for non-dry runs</li>
+ <li>GIT_NAME/GIT_EMAIL: will be used for the RC commit</li>
+ <li>GPG_KEY: id for you GPG key. The script will offer a GPG secret key from
your key ring, double check that it is your code signing key, and correct it if
it is not.</li>
+ </ul>
+ <p>The dry-run will generate the signed release files into
<tt><workdir>/output</tt> directory. The maven artifacts will be in
<tt><workdir>/output/phoenix-repo-XXXX</tt> local maven repo, in the
usual structure</p>
+</div>
+<div class="section">
+ <h2 id="Create_real_RC">Create real RC</h2>
+ <p>If the dyr-run release artifacts (source, binary, and maven) check out,
then do publish a real RC to ASF</p>
+ <p>Repeat the dry run process, but add the <tt>-f</tt> switch to the
<tt>do-release-docker.sh</tt> command.</p>
+ <p>The script will upload the source and binary release artifacts to a
directory under <tt>https://dist.apache.org/repos/dist/dev/phoenix/</tt> The
script will also deploy the maven artifacts to
<tt>https://repository.apache.org/#stagingRepositories</tt> Check that these
are present.</p>
</div>
<div class="section">
<h2 id="Voting">Voting</h2>
<ol style="list-style-type: decimal">
- <li>Svn commit binary and source tars to <a class="externalLink"
href="https://dist.apache.org/repos/dist/dev/phoenix";>https://dist.apache.org/repos/dist/dev/phoenix</a></li>
- <li>Initiate the vote email. See example <a class="externalLink"
href="https://www.mail-archive.com/dev@phoenix.apache.org/msg41202.html";>here</a></li>
+ <li>Initiate the vote email. See example <a class="externalLink"
href="https://www.mail-archive.com/dev@phoenix.apache.org/msg41202.html";>here</a>,
or use the <tt><workdir>/output/vote.txt</tt> template generated by the
script.</li>
<li>In case the RC (Release Candidate) is rejected via the vote, you will
have to repeat the above process and re-initiate the vote for the next RC (RC0,
RC1, etc.).</li>
</ol>
</div>
@@ -215,24 +262,8 @@ svn mv https://dist.apache.org/repos/dis
git tag -a v4.15.0-HBase-1.3 v4.15.0-HBase-1.3-rc1 -m "Phoenix
v4.15.0-HBase-1.3 release"
</pre>
</div></li>
- <li>Remove any obsolete releases on <a class="externalLink"
href="https://dist.apache.org/repos/dist/release/phoenix";>https://dist.apache.org/repos/dist/release/phoenix</a>
given the current release.</li>
- <li> <p>Ensure your ~/.m2/settings.xml is setup correctly: </p>
- <div class="source">
- <pre> <server>
- <id>apache.releases.https</id>
- <username> <!-- YOUR APACHE USERNAME --> </username>
- <password> <!-- YOUR APACHE PASSWORD --> </password>
- </server>
-</pre>
- </div></li>
- <li> <p>Note that the head of the branch may have progressed with patches
between the time your vote was sent out and your vote passed, so you want to
make sure that you revert the code base to the tag of the RC that passed.
Release to maven (remove release directory from local repo if present): </p>
- <div>
- <pre>
-mvn clean deploy gpg:sign -DperformRelease=true
-Dgpg.passphrase=[your_pass_phrase_here]
--Dgpg.keyname=[your_key_here] -DskipTests -P release -pl
phoenix-core,phoenix-tracing-webapp,phoenix-pherf,phoenix-client,phoenix-server
-am
-</pre>
- </div> <p><b>Note</b> <a class="externalLink"
href="https://github.com/apache/phoenix-queryserver";>phoenix-queryserver</a>
and <a class="externalLink"
href="https://github.com/apache/phoenix-connectors";>phoenix-connectors</a> have
been moved to their own repo and their releases are carried out separately.</p>
<p><b>Note</b> You may need to skip JavaDoc generation by passing in the
following flag: <tt>-Dmaven.javadoc.skip=true</tt></p></li>
- <li> <p>Go to <a class="externalLink"
href="https://repository.apache.org/#stagingRepositories";>https://repository.apache.org/#stagingRepositories</a>
and <tt>close</tt> -> <tt>release</tt> the staged artifacts (takes a while
so you may need to <tt>refresh</tt> multiple times).</p></li>
+ <li> <p>Remove any obsolete releases on <a class="externalLink"
href="https://dist.apache.org/repos/dist/release/phoenix";>https://dist.apache.org/repos/dist/release/phoenix</a>
given the current release.</p></li>
+ <li>Go to <a class="externalLink"
href="https://repository.apache.org/#stagingRepositories";>https://repository.apache.org/#stagingRepositories</a>
and <tt>close</tt> -> <tt>release</tt> the staged artifacts (takes a while
so you may need to <tt>refresh</tt> multiple times).</li>
<li>Create new branch based on current release if needed, for ex: 4.15
branches in this case.</li>
<li> <p>Set version to the upcoming SNAPSHOT and commit:</p>
<div>
@@ -240,7 +271,7 @@ mvn clean deploy gpg:sign -DperformRelea
mvn versions:set -DnewVersion=4.16.0-HBase-1.3-SNAPSHOT
-DgenerateBackupPoms=false
</pre>
</div></li>
- <li>Create a JIRA to update PHOENIX_MAJOR_VERSION, PHOENIX_MINOR_VERSION and
PHOENIX_PATCH_NUMBER in MetaDataProtocol.java appropriately to next version (4,
16, 0 respectively in this case) and compatible_client_versions.json file with
the client versions that are compatible against the next version ( In this case
4.14.3 and 4.15.0 would be the backward compatible clients for 4.16.0 ). This
Jira should be committed/marked with fixVersion of the next release
candidate.</li>
+ <li>If releasing Phoenix (core) Create a JIRA to update
PHOENIX_MAJOR_VERSION, PHOENIX_MINOR_VERSION and PHOENIX_PATCH_NUMBER in
MetaDataProtocol.java appropriately to next version (4, 16, 0 respectively in
this case) and compatible_client_versions.json file with the client versions
that are compatible against the next version ( In this case 4.14.3 and 4.15.0
would be the backward compatible clients for 4.16.0 ). This Jira should be
committed/marked with fixVersion of the next release candidate.</li>
<li>Add documentation of released version to the <a class="externalLink"
href="http://phoenix.apache.org/download.html";>downloads page</a> and <a
class="externalLink"
href="https://en.wikipedia.org/wiki/Apache_Phoenix";>wiki</a>.</li>
<li>Send out an announcement email. See example <a class="externalLink"
href="https://www.mail-archive.com/dev@phoenix.apache.org/msg54764.html";>here</a>.</li>
<li>Bulk close Jiras that were marked for the release fixVersion.</li>
@@ -497,7 +528,7 @@ mvn versions:set -DnewVersion=4.16.0-HBa
<div class="row">
<div class="span12">
<p class="pull-right"><a href="#">Back to
top</a></p>
- <p class="copyright">Copyright ©2020 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
+ <p class="copyright">Copyright ©2021 <a
href="http://www.apache.org";>Apache Software Foundation</a>. All Rights
Reserved.</p>
</div>
</div>
</div>
Modified: phoenix/site/source/src/site/markdown/release.md
URL:
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/release.md?rev=1885967&r1=1885966&r2=1885967&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/release.md (original)
+++ phoenix/site/source/src/site/markdown/release.md Thu Jan 28 08:00:32 2021
@@ -1,25 +1,89 @@
# How to do a release
-Following instructions walks you through releasing Phoenix-4.15.0-HBase-1.3.
These steps needs to be repeated for all HBase branches.
-## Pre-Reqs
-1. Make sure you have setup your user for release signing. Details
http://www.apache.org/dev/release-signing.html.
-2. Clone the branch locally from which you want to do a release.
-3. Set version to release and commit.
+Phoenix has several repos, phoenix-thirdparty, phoenix-omid, phoenix-tephra,
phoenix, phoenix-connectors and phoenix-queryserver
+The create-release scripts provide a unified script to handle the release from
each repo.
+The create-release scripts are in the master branch phoenix repo, in the
dev/create-release directory.
- <pre>
- mvn versions:set -DnewVersion=4.15.0-HBase-1.3 -DgenerateBackupPoms=false
- </pre>
-## Build binary and source tars
-
- <pre>
- $ cd dev; ./make_rc.sh
- </pre>
-Follow the instructions. Signed binary and source tars will be generated in
the _release_ directory. As last part of this script, it will ask if you want
to tag the branch at this time (sample tag: `v4.15.0-HBase-1.3-rc0`). If all
looks good then svn commit binary and source tars to
https://dist.apache.org/repos/dist/dev/phoenix
+## Pre-Reqs
+1. Make sure that the JIRAs included in the release have their fix-version and
release notes fields set correctly, and are resolved.
+The script will query them, and create the CHANGES and RELEASE_NOTES files
from that information.
+2. Make sure you have set up your user for release signing. Details
http://www.apache.org/dev/release-signing.html.
+3. Make sure you have set up maven for deploying to the ASF repo. Details
https://infra.apache.org/publishing-maven-artifacts.html
+4. Clone the phoenix master branch locally (the script will download the
actual repo to release itself)
+5. Make sure docker is running locally
+
+Note that Docker Desktop for Mac works, but will be slow. (Several hours for
for a phoenix (core) release ).
+Running on a native Linux machine is much faster, as you do not incur the
filesystem translation layer penalty
+
+## Do a dry run
+
+Read /dev/create\_release/README.txt to get an idea of what the script does,
and how to set up gpg-agent for signing.
+
+Run the `dev/create-release/do-release-docker.sh -d <workdir> -p <project>`
command, where
+
+- `<project>` is the repo name you're releasing from (i.e. phoenix)
+- `<workdir>` is any existing directory that can be deleted
+
+The script will ask a number of questions. Some of them will have intelligent
default, but make sure you check them all:
+
+```
+ [stoty@IstvanToth-MBP15:~/workspaces/apache-phoenix/phoenix
(PHOENIX-6307)$]dev/create-release/do-release-docker.sh -p phoenix -d
~/x/phoenix-build/
+ Output directory already exists. Overwrite and continue? [y/n] y
+ ========================
+ === Gathering release details.
+
+ PROJECT [phoenix]:
+ GIT_BRANCH []: master
+ Current branch VERSION is 5.1.0-SNAPSHOT.
+ RELEASE_VERSION [5.1.0]:
+ RC_COUNT [0]:
+ RELEASE_TAG [5.1.0RC0]:
+ This is a dry run. If tag does not actually exist, please confirm the ref
that will be built for testing.
+ GIT_REF [5.1.0RC0]:
+ ASF_USERNAME [stoty]:
+ GIT_NAME [Istvan Toth]:
+ GPG_KEY [st...@apache.org]:
+ We think the key 'st...@apache.org' corresponds to the key id '0x77E592D4'.
Is this correct [y/n]? y
+ ================
+ Release details:
+ GIT_BRANCH: master
+ RELEASE_VERSION: 5.1.0
+ RELEASE_TAG: 5.1.0RC0
+ API_DIFF_TAG:
+ ASF_USERNAME: stoty
+ GPG_KEY: 0x77E592D4
+ GIT_NAME: Istvan Toth
+ GIT_EMAIL: st...@apache.org
+ DRY_RUN: yes
+ ================
+```
+
+- PROJECT: the repo to release (default specified by -p on the command line)
+- GIT\_BRANCH: the git branch to use for release. This can be master, or a
pre-created release branch.
+- RC\_COUNT: the RC number, starting from 0
+- RELEASE\_TAG: the git tag the the script will tag the RC commit with.
+- ASF_USERNAME: your ASF username, for publishing the release artifacts.
+- ASF\_PASSOWORD: your ASF password, only for non-dry runs
+- GIT\_NAME/GIT\_EMAIL: will be used for the RC commit
+- GPG\_KEY: id for you GPG key. The script will offer a GPG secret key from
your key ring, double check that it is your code signing key, and correct it if
it is not.
+
+
+The dry-run will generate the signed release files into `<workdir>/output`
directory.
+The maven artifacts will be in `<workdir>/output/phoenix-repo-XXXX` local
maven repo, in the usual structure
+
+## Create real RC
+
+If the dyr-run release artifacts (source, binary, and maven) check out, then
do publish a real RC to ASF
+
+Repeat the dry run process, but add the `-f` switch to the
`do-release-docker.sh` command.
+
+The script will upload the source and binary release artifacts to a directory
under `https://dist.apache.org/repos/dist/dev/phoenix/`
+The script will also deploy the maven artifacts to
`https://repository.apache.org/#stagingRepositories`
+Check that these are present.
## Voting
-1. Svn commit binary and source tars to
https://dist.apache.org/repos/dist/dev/phoenix
-2. Initiate the vote email. See example
[here](https://www.mail-archive.com/dev@phoenix.apache.org/msg41202.html)
-3. In case the RC (Release Candidate) is rejected via the vote, you will have
to repeat the above process and re-initiate the vote for the next RC (RC0, RC1,
etc.).
+1. Initiate the vote email. See example
[here](https://www.mail-archive.com/dev@phoenix.apache.org/msg41202.html), or
use the `<workdir>/output/vote.txt` template generated by the script.
+2. In case the RC (Release Candidate) is rejected via the vote, you will have
to repeat the above process and re-initiate the vote for the next RC (RC0, RC1,
etc.).
## Release
1. Once voting is successful (say for RC1), copy artifacts to
https://dist.apache.org/repos/dist/release/phoenix:
@@ -34,37 +98,16 @@ Follow the instructions. Signed binary a
<pre>
git tag -a v4.15.0-HBase-1.3 v4.15.0-HBase-1.3-rc1 -m "Phoenix
v4.15.0-HBase-1.3 release"
</pre>
+
3. Remove any obsolete releases on
https://dist.apache.org/repos/dist/release/phoenix given the current release.
-
-4. Ensure your ~/.m2/settings.xml is setup correctly:
-
- ```
- <server>
- <id>apache.releases.https</id>
- <username> <!-- YOUR APACHE USERNAME --> </username>
- <password> <!-- YOUR APACHE PASSWORD --> </password>
- </server>
- ```
-
-5. Note that the head of the branch may have progressed with patches between
the time your vote was sent out and your vote passed, so you want to make sure
that you revert the code base to the tag of the RC that passed. Release to
maven (remove release directory from local repo if present):
-
- <pre>
- mvn clean deploy gpg:sign -DperformRelease=true
-Dgpg.passphrase=[your_pass_phrase_here]
- -Dgpg.keyname=[your_key_here] -DskipTests -P release -pl
phoenix-core,phoenix-tracing-webapp,phoenix-pherf,phoenix-client,phoenix-server
-am
- </pre>
-
- **Note**
[phoenix-queryserver](https://github.com/apache/phoenix-queryserver) and
[phoenix-connectors](https://github.com/apache/phoenix-connectors) have been
moved to their own repo and their releases are carried out separately.
-
- **Note** You may need to skip JavaDoc generation by passing in the
following flag: `-Dmaven.javadoc.skip=true `
-
-6. Go to https://repository.apache.org/#stagingRepositories and
<code>close</code> -> <code>release</code> the staged artifacts (takes a while
so you may need to `refresh` multiple times).
+4. Go to https://repository.apache.org/#stagingRepositories and
<code>close</code> -> <code>release</code> the staged artifacts (takes a while
so you may need to `refresh` multiple times).
7. Create new branch based on current release if needed, for ex: 4.15 branches
in this case.
8. Set version to the upcoming SNAPSHOT and commit:
<pre>
mvn versions:set -DnewVersion=4.16.0-HBase-1.3-SNAPSHOT
-DgenerateBackupPoms=false
</pre>
-9. Create a JIRA to update PHOENIX_MAJOR_VERSION, PHOENIX_MINOR_VERSION and
PHOENIX_PATCH_NUMBER in MetaDataProtocol.java appropriately to next version (4,
16, 0 respectively in this case) and compatible_client_versions.json file with
the client versions that are compatible against the next version ( In this case
4.14.3 and 4.15.0 would be the backward compatible clients for 4.16.0 ). This
Jira should be committed/marked with fixVersion of the next release candidate.
+9. If releasing Phoenix (core) Create a JIRA to update PHOENIX_MAJOR_VERSION,
PHOENIX_MINOR_VERSION and PHOENIX_PATCH_NUMBER in MetaDataProtocol.java
appropriately to next version (4, 16, 0 respectively in this case) and
compatible_client_versions.json file with the client versions that are
compatible against the next version ( In this case 4.14.3 and 4.15.0 would be
the backward compatible clients for 4.16.0 ). This Jira should be
committed/marked with fixVersion of the next release candidate.
10. Add documentation of released version to the [downloads
page](http://phoenix.apache.org/download.html) and
[wiki](https://en.wikipedia.org/wiki/Apache_Phoenix).
11. Send out an announcement email. See example
[here](https://www.mail-archive.com/dev@phoenix.apache.org/msg54764.html).
12. Bulk close Jiras that were marked for the release fixVersion.
