Document branches and publishing for the docs site properly. about docs HOT 3 CLOSED

The next-release branch is not sufficient. It provides no way for users
to access docs that are correct for the versions (Prometheus, Alertmanager,
...) they are running, which will become increasingly important in the
future.

On Fri, Jan 15, 2016 at 8:26 PM Björn Rabenstein [email protected]
wrote:

We need to clearly document at various places that prometheus.io is based
on HEAD and represents the latest releases of the various other repos,
while unreleased features (in the HEAD of the various repos) are in the
next-releas branch of docs.

Currently, we document something completely wrong on
http://prometheus.io/docs/introduction/install/ :
"Note that this documentation (as published on prometheus.io) refers to
the latest production release. The head of the prometheus/docs GitHub
repository refers to the (possibly not yet released) head of the
prometheus/prometheus (and other) repositories."

—
Reply to this email directly or view it on GitHub
#292.

from docs.

Post 1.0, we should definitely have "versioned" docs. Pre 1.0, I think the overhead is prohibitive.

from docs.

The wrong documentation was removed in #405.

from docs.