From 038be29ea39283ab55bd954ffce608965163c922 Mon Sep 17 00:00:00 2001 From: Paul Marshall Date: Fri, 23 Aug 2019 13:32:25 -0500 Subject: [PATCH] Preparing the 1.0.10 release --- CHANGELOG.md | 10 ++++++++++ release/RELEASE.md | 6 +++--- 2 files changed, 13 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index acae217c..9c78400d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,13 @@ +# 1.0.10 (2019-08-23) + +Modifications: +* Removed ASGs and ELBs for ZooKeeper instances +* Gather additional log files for Stardog 7 + +Fixes: +* Preserve arguments passed to stardog server start +* Download ZooKeeper from archive instead of mirrors + # 1.0.9 (2018-06-05) Fixes: diff --git a/release/RELEASE.md b/release/RELEASE.md index 33fc1afc..b946ed54 100644 --- a/release/RELEASE.md +++ b/release/RELEASE.md @@ -2,11 +2,11 @@ 1. Make the release branch from `master`, e.g.: `release/1.0.9` 1. Update `CHANGELOG.md` manually with a helpful description of any commits that have landed since the last release. +1. Tag the release: `git tag 1.0.9` 1. Run `make clean && make` 1. Verify the version string matches the new release and latest git hash (just with `stardog-graviton --version` on the new binary) 1. Run `make test` -1. Run: `python release/release.py ` -1. Once the tests all pass, tag the release in the branch, e.g.: `git tag 1.0.9` -1. Push up the release branch and tag +1. Run: `python release/release.py `. This runs in us-west-1 so make sure the key exists in that region. +1. Once the tests pass, push up the release branch and tag: `git push origin release/1.0.9` and `git push origin ` 1. The release files can be found at `release/darwin_amd64/stardog-graviton__darwin_amd64.zip` and `release/linux_amd64/stardog-graviton__linux_amd64.zip`. Upload them to the newly found release here: https://github.com/stardog-union/stardog-graviton/releases 1. PR the release branch to master and merge it