You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@calcite.apache.org by fr...@apache.org on 2019/05/09 09:09:25 UTC

[calcite-avatica] 01/01: [CALCITE-3058] Prepare for 1.15.0 release

This is an automated email from the ASF dual-hosted git repository.

francischuang pushed a commit to branch branch-avatica-1.15
in repository https://gitbox.apache.org/repos/asf/calcite-avatica.git

commit b9df4bdd4930610a755678b6e460c8f12c90242b
Author: Francis Chuang <fr...@apache.org>
AuthorDate: Thu May 9 19:04:22 2019 +1000

    [CALCITE-3058] Prepare for 1.15.0 release
---
 README                      |  2 +-
 pom.xml                     |  2 +-
 site/_docs/docker_images.md | 28 ++++++++++++++--------------
 site/_docs/history.md       | 25 +++++++++++++++++++++++++
 site/_docs/howto.md         | 12 ++++++------
 5 files changed, 47 insertions(+), 22 deletions(-)

diff --git a/README b/README
index 9bee033..ec2fc88 100644
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-Apache Calcite Avatica release 1.14.0
+Apache Calcite Avatica release 1.15.0
 
 This is a source or binary distribution of Avatica, a framework for
 building database drivers. Avatica is a sub-project of Apache Calcite.
diff --git a/pom.xml b/pom.xml
index f347602..7752699 100644
--- a/pom.xml
+++ b/pom.xml
@@ -59,7 +59,7 @@ limitations under the License.
     <top.dir>${project.basedir}</top.dir>
     <avatica.release.version>${project.version}</avatica.release.version>
     <version.major>1</version.major>
-    <version.minor>14</version.minor>
+    <version.minor>15</version.minor>
 
     <!-- This list is in alphabetical order. -->
     <apache-rat-plugin.version>0.13</apache-rat-plugin.version>
diff --git a/site/_docs/docker_images.md b/site/_docs/docker_images.md
index dba1654..cf21a3b 100644
--- a/site/_docs/docker_images.md
+++ b/site/_docs/docker_images.md
@@ -70,22 +70,22 @@ file will start an instance of PostgreSQL and an instance of the Avatica server,
 exposing an Avatica server configured against a "real" PostgreSQL database.
 
 All of the `Dockerfile` and `docker-compose.yml` files are conveniently provided in an archive for
-each release. Here is the layout for release 1.14.0:
+each release. Here is the layout for release 1.15.0:
 
 ```
-avatica-docker-1.14.0/
-avatica-docker-1.14.0/hypersql/
-avatica-docker-1.14.0/mysql/
-avatica-docker-1.14.0/postgresql/
-avatica-docker-1.14.0/Dockerfile
-avatica-docker-1.14.0/hypersql/build.sh
-avatica-docker-1.14.0/hypersql/Dockerfile
-avatica-docker-1.14.0/mysql/build.sh
-avatica-docker-1.14.0/mysql/docker-compose.yml
-avatica-docker-1.14.0/mysql/Dockerfile
-avatica-docker-1.14.0/postgresql/build.sh
-avatica-docker-1.14.0/postgresql/docker-compose.yml
-avatica-docker-1.14.0/postgresql/Dockerfile
+avatica-docker-1.15.0/
+avatica-docker-1.15.0/hypersql/
+avatica-docker-1.15.0/mysql/
+avatica-docker-1.15.0/postgresql/
+avatica-docker-1.15.0/Dockerfile
+avatica-docker-1.15.0/hypersql/build.sh
+avatica-docker-1.15.0/hypersql/Dockerfile
+avatica-docker-1.15.0/mysql/build.sh
+avatica-docker-1.15.0/mysql/docker-compose.yml
+avatica-docker-1.15.0/mysql/Dockerfile
+avatica-docker-1.15.0/postgresql/build.sh
+avatica-docker-1.15.0/postgresql/docker-compose.yml
+avatica-docker-1.15.0/postgresql/Dockerfile
 ```
 
 #### Running
diff --git a/site/_docs/history.md b/site/_docs/history.md
index 0ac1f37..2d0da73 100644
--- a/site/_docs/history.md
+++ b/site/_docs/history.md
@@ -28,6 +28,31 @@ For a full list of releases, see
 Downloads are available on the
 [downloads page]({{ site.baseurl }}/downloads/avatica.html).
 
+## <a href="https://github.com/apache/calcite-avatica/releases/tag/rel/avatica-1.15.0">1.15.0</a> / 2019-05-XX
+{: #v1-15-0}
+
+Apache Calcite Avatica 1.15.0 is a small release that reverts CALCITE-2845 due to some incompatibilities with downstream
+clients.
+
+Compatibility: This release is tested
+on Linux, macOS, Microsoft Windows;
+using Oracle JDK 8, 9, 10, 11, 12, 13;
+using IBM Java 8;
+Guava versions 14.0 to 23.0;
+other software versions as specified in `pom.xml`.
+
+Features and bug fixes
+
+* [<a href="https://issues.apache.org/jira/browse/CALCITE-3043">CALCITE-3043</a>]
+  Add the ability to publish and promote releases using docker
+* [<a href="https://issues.apache.org/jira/browse/CALCITE-3040">CALCITE-3040</a>]
+  Revert CALCITE-2845 due to incompatibilities with downstream clients
+
+Website and Documentation
+
+* [<a href="https://issues.apache.org/jira/browse/CALCITE-3033">CALCITE-3033</a>]
+  Add navigation item for avatica-go HOWTO documentation
+
 ## <a href="https://github.com/apache/calcite-avatica/releases/tag/rel/avatica-1.14.0">1.14.0</a> / 2019-04-29
 {: #v1-14-0}
 
diff --git a/site/_docs/howto.md b/site/_docs/howto.md
index 20a955b..a3344e1 100644
--- a/site/_docs/howto.md
+++ b/site/_docs/howto.md
@@ -38,8 +38,8 @@ Unpack the source distribution `.tar.gz` file,
 then build using maven:
 
 {% highlight bash %}
-$ tar xvfz apache-calcite-avatica-1.14.0-src.tar.gz
-$ cd apache-calcite-avatica-1.14.0-src
+$ tar xvfz apache-calcite-avatica-1.15.0-src.tar.gz
+$ cd apache-calcite-avatica-1.15.0-src
 $ ./mvnw install
 {% endhighlight %}
 
@@ -220,10 +220,10 @@ To perform the dry-run, you can either use your environment or the release scrip
 git clean -xn
 
 # Do a dry run of the release:prepare step, which sets version numbers.
-# Typically we increment minor version: If X.Y.Z is 1.14.0, X2.Y2.Z2 is 1.15.0.
+# Typically we increment minor version: If X.Y.Z is 1.15.0, X2.Y2.Z2 is 1.16.0.
 # Note X.Y.Z is the current version we're trying to release, and X2.Y2.Z2 is the next development version.
 
-# For example, if I am currently building a release for 1.14.0, X.Y.Z would be 1.14.0 and X2.Y2.Z2 would be 1.15.0.
+# For example, if I am currently building a release for 1.15.0, X.Y.Z would be 1.15.0 and X2.Y2.Z2 would be 1.16.0.
 ./mvnw -DdryRun=true -DreleaseVersion=X.Y.Z -DdevelopmentVersion=X2.Y2.Z2-SNAPSHOT -Dtag=avatica-X.Y.Z-rcN -Papache-release -Duser.name=${asf.username} release:prepare
 
 # If you have multiple GPG keys, you can select the key used to sign the release by appending `-Dgpg.keyname=${your.key.id}` to `-Darguments`:
@@ -290,9 +290,9 @@ If successful, remove the `-DdryRun` flag and run the release for real.
 
 {% highlight bash %}
 # Prepare sets the version numbers, creates a tag, and pushes it to git.
-# Typically we increment minor version: If X.Y.Z is 1.14.0, X2.Y2.Z2 is 1.15.0.
+# Typically we increment minor version: If X.Y.Z is 1.15.0, X2.Y2.Z2 is 1.16.0.
 # Note X.Y.Z is the current version we're trying to release, and X2.Y2.Z2 is the next development version.
-# For example, if I am currently building a release for 1.14.0, X.Y.Z would be 1.14.0 and X2.Y2.Z2 would be 1.15.0.
+# For example, if I am currently building a release for 1.15.0, X.Y.Z would be 1.15.0 and X2.Y2.Z2 would be 1.16.0.
 ./mvnw -DreleaseVersion=X.Y.Z -DdevelopmentVersion=X2.Y2.Z2-SNAPSHOT -Dtag=avatica-X.Y.Z-rcN -Papache-release -Duser.name=${asf.username} release:prepare
 
 # If you have multiple GPG keys, you can select the key used to sign the release by appending `-Darguments=-Dgpg.keyname=${your.key.id}`: