diff options
| author | Dave Whiteland <dave@mysociety.org> | 2014-06-17 17:28:17 +0200 |
|---|---|---|
| committer | Dave Whiteland <dave@mysociety.org> | 2014-06-17 17:28:17 +0200 |
| commit | 0ca1a6446b8ccd6345227a4ac5c1a31bf90a558b (patch) | |
| tree | f6479f66d10df2a28819fffc2b31c4b2ffc803f4 /docs/running/upgrading.md | |
| parent | 2bc37caf36699133392ba20d91d4f7baa0dbd936 (diff) | |
rewrite first para to refer to specific release tags
It's true it's on master, but unwise to use that in production.
Also, it's helpful to link to the releases on github!
Diffstat (limited to 'docs/running/upgrading.md')
| -rw-r--r-- | docs/running/upgrading.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/running/upgrading.md b/docs/running/upgrading.md index 6088d9ab1..4074e7a14 100644 --- a/docs/running/upgrading.md +++ b/docs/running/upgrading.md @@ -14,8 +14,11 @@ Upgrading Alaveteli ## Master branch contains the latest stable release The developer team policy is that the `master` branch in git should always -contain the latest stable release. Therefore, in production, you should usually -have your software deployed from the `master` branch. +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 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). Upgrading may just require pulling in the latest code -- but it may also require other changes ("further action"). For this reason, for anything other than a |