[ckan-changes] [okfn/ckan] 45ae2e: [#969] Add instructions for package patch upgrades
GitHub
noreply at github.com
Wed Jun 5 16:51:14 UTC 2013
Branch: refs/heads/master
Home: https://github.com/okfn/ckan
Commit: 45ae2ec72198fb6c72f0e594f610c0c882d6781b
https://github.com/okfn/ckan/commit/45ae2ec72198fb6c72f0e594f610c0c882d6781b
Author: amercader <amercadero at gmail.com>
Date: 2013-06-04 (Tue, 04 Jun 2013)
Changed paths:
M doc/upgrading-a-package-install.rst
Log Message:
-----------
[#969] Add instructions for package patch upgrades
Commit: 7ced50e7708db8cb819f9c3a24adb7ca3a5089ae
https://github.com/okfn/ckan/commit/7ced50e7708db8cb819f9c3a24adb7ca3a5089ae
Author: Sean Hammond <seanhammond at lavabit.com>
Date: 2013-06-05 (Wed, 05 Jun 2013)
Changed paths:
M doc/conf.py
M doc/upgrading-a-package-install.rst
Log Message:
-----------
[#969] Edit the upgrading to a patch release docs
- Group the *Upgrading to a patch version* and *Upgrading a 1.X Package
Install to CKAN 2.0* section headings under a top-level *Upgrading a
package install* heading (this is just so that only one *Upgrading a
package install* heading appears in the table of contents)
- Edit the first couple of paragraphs of *Upgrading to a patch version*
a little
- Say CKAN config file not ini file
- Use |apache| and |nginx| to get correct capitalisation of those names
Commit: abbeb4407f34ac341b76110fe36f09e09dff35eb
https://github.com/okfn/ckan/commit/abbeb4407f34ac341b76110fe36f09e09dff35eb
Author: Sean Hammond <seanhammond at lavabit.com>
Date: 2013-06-05 (Wed, 05 Jun 2013)
Changed paths:
M doc/conf.py
M doc/upgrading-a-package-install.rst
Log Message:
-----------
Merge branch '969-upgrade-patch-instructions'
Compare: https://github.com/okfn/ckan/compare/c7138345c2ef...abbeb4407f34
More information about the ckan-changes
mailing list