summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorSteve Piercy <web@stevepiercy.com>2016-11-25 19:20:34 -0800
committerSteve Piercy <web@stevepiercy.com>2016-11-25 19:20:34 -0800
commit78254d48a39e2b4938297dd568b02ab055b54c3f (patch)
tree05b1d23094e287e2e9b66751f0d226aee9f10873 /docs
parentf4518e72c82ad3ef7aeba65ad1221924767b32ea (diff)
downloadpyramid-78254d48a39e2b4938297dd568b02ab055b54c3f.tar.gz
pyramid-78254d48a39e2b4938297dd568b02ab055b54c3f.tar.bz2
pyramid-78254d48a39e2b4938297dd568b02ab055b54c3f.zip
add feature versioning, seealso
Diffstat (limited to 'docs')
-rw-r--r--docs/style-guide.rst84
1 files changed, 84 insertions, 0 deletions
diff --git a/docs/style-guide.rst b/docs/style-guide.rst
index f13671704..51a2efde5 100644
--- a/docs/style-guide.rst
+++ b/docs/style-guide.rst
@@ -763,6 +763,70 @@ The above code renders as follows.
+------------------------+------------+---------------------+
+.. _style-guide-feature-versioning:
+
+Feature versioning
+^^^^^^^^^^^^^^^^^^
+
+Three directives designate the version in which something is added, changed, or deprecated in the project.
+
+
+.. _style-guide-version-added:
+
+Version added
+`````````````
+
+To indicate the version in which a feature is added to a project, use the ``versionadded`` directive. If the feature is an entire module, then the directive should be placed at the top of the module section before any prose.
+
+The first argument is the version. An optional second argument must appear upon a subsequent line, without blank lines in between, and indented.
+
+.. code-block:: rst
+
+ .. versionadded:: 1.1
+ :func:`pyramid.paster.bootstrap`
+
+The above code renders as follows.
+
+.. versionadded:: 1.1
+ :func:`pyramid.paster.bootstrap`
+
+
+.. _style-guide-version-changed:
+
+Version changed
+```````````````
+
+To indicate the version in which a feature is changed in a project, use the ``versionchanged`` directive. Its arguments are the same as ``versionadded``.
+
+.. code-block:: rst
+
+ .. versionchanged:: 1.8
+ Added the ability for ``bootstrap`` to cleanup automatically via the ``with`` statement.
+
+The above code renders as follows.
+
+.. versionchanged:: 1.8
+ Added the ability for ``bootstrap`` to cleanup automatically via the ``with`` statement.
+
+
+.. _style-guide-deprecated:
+
+Deprecated
+``````````
+
+Similar to ``versionchanged``, ``deprecated`` describes when the feature was deprecated. An explanation can also be given, for example, to inform the reader what should be used instead.
+
+.. code-block:: rst
+
+ .. deprecated:: 1.7
+ Use the ``require_csrf`` option or read :ref:`auto_csrf_checking` instead to have :class:`pyramid.exceptions.BadCSRFToken` exceptions raised.
+
+The above code renders as follows.
+
+.. deprecated:: 1.7
+ Use the ``require_csrf`` option or read :ref:`auto_csrf_checking` instead to have :class:`pyramid.exceptions.BadCSRFToken` exceptions raised.
+
+
.. _style-guide-danger:
Danger
@@ -827,6 +891,26 @@ The above code renders as follows.
This is a note.
+.. _style-guide-see-also:
+
+See also
+^^^^^^^^
+
+"See also" messages refer to topics that are related to the current topic, but have a narrative tone to them instead of merely a link without explanation. "See also" is rendered in a block as well, so that it stands out for the reader's attention.
+
+.. code-block:: rst
+
+ .. seealso::
+
+ See :ref:`Quick Tutorial section on Requirements <qtut_requirements>`.
+
+The above code renders as follows.
+
+.. seealso::
+
+ See :ref:`Quick Tutorial section on Requirements <qtut_requirements>`.
+
+
.. _style-guide-todo:
Todo