readthedocs.org/docs/versions.rst

53 lines
2.0 KiB
ReStructuredText
Raw Normal View History

2014-01-04 02:08:24 +00:00
Versions
========
Read the Docs supports multiple versions of your repository.
On the initial import,
we will create a ``latest`` version.
This will point at the default branch for your VCS control: ``master``, ``default``, or ``trunk``.
2014-10-19 20:47:51 +00:00
We also create a ``stable`` version,
2015-01-26 18:08:58 +00:00
if your project has any tagged releases.
2014-10-19 20:47:51 +00:00
``stable`` will be automatically kept up to date to point at your highest version.
2014-01-04 02:11:00 +00:00
How we envision versions working
2014-01-04 02:08:24 +00:00
--------------------------------
In the normal case,
the ``latest`` version will always point to the most up to date development code.
If you develop on a branch that is different than the default for your VCS,
you should set the **Default Branch** to that branch.
You should push a **tag** for each version of your project.
These tags should be numbered in a way that is consistent with `semantic versioning <http://semver.org/>`_.
2014-10-19 20:49:28 +00:00
This will map to your ``stable`` branch by default.
2014-01-04 02:08:24 +00:00
.. note::
We in fact are parsing your tag names against the rules given by
`PEP 440`_. This spec allows "normal" version numbers like ``1.4.2`` as
well as pre-releases. An alpha version or a release candidate are examples
of pre-releases and they look like this: ``2.0a1``.
We only consider non pre-releases for the ``stable`` version of your
documentation.
2014-01-04 02:13:34 +00:00
If you have documentation changes on a **long-lived branch**,
2014-01-04 02:08:24 +00:00
you can build those too.
This will allow you to see how the new docs will be built in this branch of the code.
Generally you won't have more than 1 active branch over a long period of time.
2014-01-04 02:13:34 +00:00
The main exception here would be **release branches**,
2014-01-04 02:08:24 +00:00
which are branches that are maintained over time for a specific release number.
.. _PEP 440: https://www.python.org/dev/peps/pep-0440/
2014-01-04 02:08:24 +00:00
Redirects on root URLs
----------------------
When a user hits the root URL for your documentation,
2016-04-27 23:14:36 +00:00
for example ``http://pip.readthedocs.io/``,
2014-01-17 13:38:30 +00:00
they will be redirected to the **Default version**.
2014-01-04 02:08:24 +00:00
This defaults to **latest**,
but could also point to your latest released version.