aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSitaram Chamarty <sitaram@atc.tcs.com>2010-05-19 13:53:18 +0530
committerSitaram Chamarty <sitaram@atc.tcs.com>2010-05-19 14:33:35 +0530
commit3ddc8aa0ca70b956595fa9982e5a793105af9743 (patch)
treeb8072021be0c5e9890975d9d168b052b8f3a7ab7
parent(big-config) doc fixup (diff)
downloadgitolite-gentoo-1.5.tar.gz
gitolite-gentoo-1.5.tar.bz2
gitolite-gentoo-1.5.zip
(important upgrade info here)v1.5
There has been a format change to the compiled output file. As the CHANGELOG says: Upgrading to v1.5 from any version prior to v1.5 requires an extra step for people who installed gitolite using the "system install / user setup" method described in doc/0-INSTALL.mkd. For such installations, after the administrator has upgraded gitolite system-wide, each "gitolite host" user must run `gl-setup` once (without any arguments). This is *not* an issue if you installed using src/gl-easy-install.
-rw-r--r--doc/0-INSTALL.mkd12
-rw-r--r--doc/CHANGELOG19
2 files changed, 29 insertions, 2 deletions
diff --git a/doc/0-INSTALL.mkd b/doc/0-INSTALL.mkd
index b1ae760..37c81cc 100644
--- a/doc/0-INSTALL.mkd
+++ b/doc/0-INSTALL.mkd
@@ -169,10 +169,18 @@ private key to clone and push it. In other words, that person is the
administrator for this particular gitolite instance.
If your system administrator upgrades gitolite itself, things will usually
-just work without any change; you should not have to do anything special.
-However, some new features may require additional settings in your
+just work without any change; you should not normally have to do anything
+special. However, some new features may require additional settings in your
`~/.gitolite.rc` file.
+> [The only exception to this is when there is a change in the format of the
+"compiler" output -- then *each* gitolite hosting user must run "`gl-setup`
+again (no arguments needed this time), to fix up the compiled file format.
+
+> Such a change will be clearly marked with "upgrade notes" both in the
+CHANGELOG and in the commit message. For example, this applies when upgrading
+to v1.5 or later from any version before it.]
+
Finally, in the rare case that you managed to lose your keys to the admin repo
and want to supply a new pubkey, you can use this command to replace any such
key. Could be useful in an emergency -- just get your new "yourname.pub" to
diff --git a/doc/CHANGELOG b/doc/CHANGELOG
index 743eeca..de1cd01 100644
--- a/doc/CHANGELOG
+++ b/doc/CHANGELOG
@@ -2,6 +2,25 @@ Major changes to gitolite, master branch only, most recent first, no dates but
the tags can help you position stuff approximately
[NYD = not yet documented due to lack of time...]
+ - v1.5 -- IMPORTANT UPGRADE NOTES below
+
+Upgrading to v1.5 from any version prior to v1.5 requires an extra step for
+people who installed gitolite using the "system install / user setup" method
+described in doc/0-INSTALL.mkd. For such installations, after the
+administrator has upgraded gitolite system-wide, each "gitolite host" user
+must run `gl-setup` once (this time without any arguments).
+
+ - "deny" rules should now work even in "big-config" due to previous change
+ - proper rule sequencing (required major format change)
+
+ - allow usergroup info to be passed in from outside, say via LDAP; see
+ doc/big-config.mkd for details
+ - (new) big-config is now part of mainline (old one had bitrotted); see
+ doc/big-config.mkd for details
+
+ - gl-system-install: help people simulate an RPM/DEB install by just running
+ that commmand with appropriate arguments; see doc/0-INSTALL.mkd
+
- admin-defined commands; see doc/admin-defined-commands.mkd
- v1.4.2 (prep for major refactor on rights queries