From 266b02dba6570b2df7dce18fbad6506af273c2e3 Mon Sep 17 00:00:00 2001 From: Matthias Schiffer <mschiffer@universe-factory.net> Date: Mon, 13 Feb 2017 02:15:00 +0100 Subject: [PATCH] docs, README: Gluon v2016.2.3 --- README.md | 2 +- docs/user/getting_started.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e16b04260..14e1fb137 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ the future development of Gluon. Please refrain from using the `master` branch for anything else but development purposes! Use the most recent release instead. You can list all relaseses by running `git tag` -and switch to one by running `git checkout v2016.2.2 && make update`. +and switch to one by running `git checkout v2016.2.3 && make update`. If you're using the autoupdater, do not autoupdate nodes with anything but releases. If you upgrade using random master commits the nodes *will break* eventually. diff --git a/docs/user/getting_started.rst b/docs/user/getting_started.rst index dd4ac422e..6c8979021 100644 --- a/docs/user/getting_started.rst +++ b/docs/user/getting_started.rst @@ -8,7 +8,7 @@ Gluon's releases are managed using `Git tags`_. If you are just getting started with Gluon we recommend to use the latest stable release of Gluon. Take a look at the `list of gluon releases`_ and notice the latest release, -e.g. *v2016.2.2*. Always get Gluon using git and don't try to download it +e.g. *v2016.2.3*. Always get Gluon using git and don't try to download it as a Zip archive as the archive will be missing version information. Please keep in mind that there is no "default Gluon" build; a site configuration @@ -43,7 +43,7 @@ Building the images ------------------- To build Gluon, first check out the repository. Replace *RELEASE* with the -version you'd like to checkout, e.g. *v2016.2.2*. +version you'd like to checkout, e.g. *v2016.2.3*. :: -- GitLab