+#
+# More specifically, you likely should try the following combinations,
+# especially if you change the protocol. Check if any data or settings get
+# lost or corrupted, or if anything unusual shows up in the log.
+#
+# [Mac/Linux]
+# Fresh configuration (reset the database and settings)
+# > SQLite
+# > New core, new client
+# > New core, old client
+# > Old core, new client
+# > New monolithic (combined core/client build)
+# > Postgres
+# > New core, new client
+# > New core, old client
+# > Old core, new client
+# Migration (set up SQLite, then --select-backend PostgreSQL)
+# > SQLite -> Postgres, new core, new client
+# Upgrading existing (set up a copy from 'master', then build your branch)
+# > SQLite
+# > Old -> new core
+# > Old monolithic -> new monolithic
+# > Postgres
+# > Old -> new core
+#
+# [Windows]
+# Fresh configuration (reset the database and settings)
+# > SQLite
+# > New core, new client
+# > New core, old client
+# > Old core, new client
+# > New monolithic (combined core/client build)
+# Upgrading existing (set up a copy from 'master', then build your branch)
+# > SQLite
+# > Old -> new core
+# > Old monolithic -> new monolithic
+# (If someone figures out how Postgres runs on Windows with Quassel, please
+# update this comment)
+#
+# Yes, this looks excessive, and maybe it is. But it's easy to overlook
+# some minor typo that breaks the client/core for a certain configuration.
+# People may get unhappy and rioting might happen in the streets. And we don't
+# want that, do we?
+#
+# Thank you for reading this guide and good luck with your changes!