summaryrefslogtreecommitdiff
path: root/doc/upgrade.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2017-09-30 19:36:49 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2017-09-30 19:36:49 +0000
commit12496b9b720a0b218827307c46c196e648a3dc76 (patch)
tree4e94be3c9e5fcd69adbb0162f3cf827ca4550c71 /doc/upgrade.html
parent059fa111e3f083930dff144a8d6f0119e84831bd (diff)
downloads6-rc-12496b9b720a0b218827307c46c196e648a3dc76.tar.xz
doc: mention when to recompile service databases
Diffstat (limited to 'doc/upgrade.html')
-rw-r--r--doc/upgrade.html12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/upgrade.html b/doc/upgrade.html
index b49c13f..4cefb17 100644
--- a/doc/upgrade.html
+++ b/doc/upgrade.html
@@ -16,6 +16,18 @@
<a href="//skarnet.org/">skarnet.org</a>
</p>
+
+<h1> Upgrade notes for s6-rc </h1>
+
+<p>
+ As a general rule, if you change <em>major versions</em>,
+for instance if you upgrade from 0.1.0.0 to 0.2.1.2, you need
+to <em>recompile your service databases</em>, because the
+binary format is not guaranteed stable across major version
+changes. You can keep your compiled service databases across
+minor and bugfix version changes.
+</p>
+
<h1> What has changed in s6-rc </h1>
<h2> in 0.2.1.2 </h2>