hiro/releases
1
0
Fork 0
mirror of https://github.com/vale981/releases synced 2025-03-04 17:21:43 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

RTD moving to .io domain

Browse source
This commit is contained in:
Jeff Forcier 2016-04-27 15:45:35 -07:00
parent 32a9225c49
commit 5c74c68d42
4 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.rst
View file

@ -23,7 +23,7 @@ Specifically:
Some background on why this tool was created can be found in `this blog post
<http://bitprophet.org/blog/2013/09/14/a-better-changelog/>`_.
For more documentation, please see http://releases.readthedocs.org.
For more documentation, please see http://releases.readthedocs.io.
.. note::
You can install the `development version

4
docs/changelog.rst
View file

@ -6,8 +6,8 @@ Changelog
.. note::
This adds a new install-time dependency: the `semantic_version library
<https://python-semanticversion.readthedocs.org/en/latest/>`_. It's pure
Python, so installation should be trivial.
<https://python-semanticversion.readthedocs.io>`_. It's pure Python, so
installation should be trivial.
* :bug:`44` Update one of our internal docutils-related classes for
compatibility with Sphinx 1.4.x. Thanks to Gabi Davar for catch & patch.

2
docs/concepts.rst
View file

@ -333,7 +333,7 @@ use one you're familiar with from packaging systems like
* ``(>=2.0,<3.0)`` limits an issue to *just* the 2.x line, preventing its
inclusion in 1.x, 3.x or anything else.
* And so on; see the documentation for the ``Spec`` class at
https://python-semanticversion.readthedocs.org for details.
https://python-semanticversion.readthedocs.io for details.
* To be clear, **you may put any combination of major+minor version number in
these annotations**, just as with the simpler ``(1.5+)`` style format.

4
docs/usage.rst
View file

@ -84,7 +84,7 @@ Specifically:
1.3 and 1.4, you might specify ``:bug:`55 (1.3+)``` to note that bug
55 only applies to releases in 1.3 and above - not 1.2.
* A `semantic version range spec covering minor+major version numbers
<https://python-semanticversion.readthedocs.org/en/latest/reference.html#version-specifications-the-spec-class>`_
<https://python-semanticversion.readthedocs.io/en/latest/reference.html#version-specifications-the-spec-class>`_
such as ``(<2.0)`` or ``(>=1.0,<3.1)``. A more powerful version of
``(N.N+)`` allowing annotation of issues belonging to specific major
versions.
@ -104,7 +104,7 @@ Specifically:
Then build your docs; in the rendered output, ``changelog.html`` should show
issues grouped by release, as per the above rules. Examples: `Releases' own
rendered changelog
<http://releases.readthedocs.org/en/latest/changelog.html>`_, `Fabric's
<http://releases.readthedocs.io/en/latest/changelog.html>`_, `Fabric's
rendered changelog <http://www.fabfile.org/changelog.html>`_.