Create slice documentation automatically on new releases + versions

[Natenom]

The slice documentation (http://mumble.sourceforge.net/slice/) should be updated automatically on every release.

There should also be a list of the last x relevant versions of the documentation.

[hacst]

The documentation should also state which version it belongs to (git describe?).

[Kissaki]

Besides mentioning the version, we should provide multiple versions of the documentation. People will want to explicitly script for older versions (from their stable distro).

[Kissaki]

I finally uploaded a more recent slice documentation.

• http://mumble.sourceforge.net/slice/1.2.0/
• http://mumble.sourceforge.net/slice/1.2.7/
• http://mumble.sourceforge.net/slice/1.3.0/

We can not configure redirects for subpaths on our SF webspace. I removed the old slice doc, put and adequate 404 in place, enabled directory listing and added a README which is displayed on the directory listing as well.

This should be a stable slice doc structure that now provides versioning and persistent resource links.

[hacst]

We probably should place those directly on the mumble.info host or something.

[Kissaki]

Probably. I just replaced them in-place for now.
The question remains: Where is this something you speak of? :)

[mkrautz]

We could have a job in the CI/build system that uploads to an S3 bucket that has a hostname assigned (say, slice.mumble.info, ice-docs.mumble.info ... or something else).

We'd trigger it with stable builds (1.2.x), as well as snapshot builds (1.3.x). It'd automatically update as new snapshots/releases are available.

[Kissaki]

Fixed the rewrite rules for the old /slice/ URLs.

[Krzmbrzl]

I guess this has not been resolved yet?

[Kissaki]

mumble-voip/mumble-www#75

[Krzmbrzl]

Alright - In that case I'll close this issue in favor of the linked one though. No need to have 2 issues for the same thing (imo).