From 3a9d0b3a0601a3d8efbaf8fec332939c06bf1478 Mon Sep 17 00:00:00 2001 From: Dan Haywood Date: Sun, 19 Feb 2017 18:29:02 +0000 Subject: [PATCH] updates README for 1.14.0 --- README.adoc | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/README.adoc b/README.adoc index 8229fa2..c98d4e6 100644 --- a/README.adoc +++ b/README.adoc @@ -123,7 +123,7 @@ To use "out-of-the-box": org.isisaddons.module.excel isis-module-excel-dom - 1.13.6 + 1.14.0 ---- @@ -165,7 +165,7 @@ If you want to use the current `-SNAPSHOT`, then the steps are the same as above + [source,xml] ---- -1.14.0-SNAPSHOT +1.15.0-SNAPSHOT ---- * add the repository definition to pick up the most recent snapshot (we use the Cloudbees continuous integration service). We suggest defining the repository in a `<profile>`: + @@ -547,6 +547,7 @@ downloadable as an Excel spreadsheet. == Change Log +* `1.14.0` - released against Isis 1.14.0 * `1.13.6` - maximum length for sheets is 31 chars, not 30 chars. * `1.13.5.1` - patch for 1.13.5 (error with `#toExcelPivot(...)`. * `1.13.5` - released against Isis 1.13.0; includes limited support for pivot tables; link:https://github.com/isisaddons/isis-module-excel/issues/17[#17] (remove overloads for `#fromExcel()` and ``#toExcel()``). + @@ -621,7 +622,7 @@ https://oss.sonatype.org/content/repositories/snapshots[Snapshot Repo]. If you have commit access to this project (or a fork of your own) then you can create interim releases using the `interim-release.sh` script. -The idea is that this will - in a new branch - update the `dom/pom.xml` with a timestamped version (eg `1.13.6.20161122-0756`). +The idea is that this will - in a new branch - update the `dom/pom.xml` with a timestamped version (eg `1.14.0.20160222-0756`). It then pushes the branch (and a tag) to the specified remote. A CI server such as Jenkins can monitor the branches matching the wildcard `origin/interim/*` and create a build. @@ -631,12 +632,12 @@ For example: [source] ---- -sh interim-release.sh 1.13.6 origin +sh interim-release.sh 1.14.0 origin ---- where -* `1.13.6` is the base release +* `1.14.0` is the base release * `origin` is the name of the remote to which you have permissions to write to. @@ -655,8 +656,8 @@ For example: [source] ---- -sh release.sh 1.13.6 \ - 1.14.0-SNAPSHOT \ +sh release.sh 1.14.0 \ + 1.15.0-SNAPSHOT \ dan@haywood-associates.co.uk \ "this is not really my passphrase" ---- @@ -675,8 +676,7 @@ If the script completes successfully, then push changes: [source] ---- -git push origin master -git push origin 1.13.6 +git push origin master && git push origin 1.14.0 ---- If the script fails to complete, then identify the cause, perform a `git reset --hard` to start over and fix the issue