diff options
author | Louise Crow <louise.crow@gmail.com> | 2014-07-10 16:56:52 +0100 |
---|---|---|
committer | Louise Crow <louise.crow@gmail.com> | 2014-07-10 16:56:52 +0100 |
commit | 95616048a07b1f34c25eb9c27875f18406a72743 (patch) | |
tree | a75fe64914466f613f5c699ed81962fd8e132424 /docs/running/upgrading.md | |
parent | 94abbed71e60f78beb5e195d00275a70ce2efc38 (diff) | |
parent | 2def92faf3b07ffb33a1fe89dac7e4208889e54a (diff) |
Merge branch 'gh-pages' of ssh://git.mysociety.org/data/git/public/alaveteli into gh-pages
Diffstat (limited to 'docs/running/upgrading.md')
-rw-r--r-- | docs/running/upgrading.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/running/upgrading.md b/docs/running/upgrading.md index 2142bfd47..ab8db2385 100644 --- a/docs/running/upgrading.md +++ b/docs/running/upgrading.md @@ -17,7 +17,7 @@ Upgrading Alaveteli The developer team policy is that the `master` branch in git should always contain the latest stable release -- so you'll be up to date if you pull from the `master` branch. However, on your -<a href="{{site.baseurl}}docs/glossary/#production" class="glossary">production +<a href="{{site.baseurl}}docs/glossary/#production" class="glossary__link">production site</a>, you should know precisely what version you're running, and deploy Alaveteli from a [*specific* release tag](https://github.com/mysociety/alaveteli/releases). |