summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTristan Van Berkom <tristan.vanberkom@codethink.co.uk>2020-04-23 21:58:34 +0900
committerTristan Van Berkom <tristan.vanberkom@codethink.co.uk>2020-04-25 00:16:01 +0900
commit1ef604f93db18c5a67bb66f1e28f952c3880a6fb (patch)
treec382af3f80e5117a7566c422f6c438a3ab378e20 /doc
parente5e776c4f0017632c6c7497ca9410aa66370278b (diff)
downloadbuildstream-1ef604f93db18c5a67bb66f1e28f952c3880a6fb.tar.gz
doc/source/hacking/writing_plugins.rst: Remove some docs about format-version
This will be done differently in BuildStream 2, as explained in this email: https://mail.gnome.org/archives/buildstream-list/2020-April/msg00017.html
Diffstat (limited to 'doc')
-rw-r--r--doc/source/hacking/writing_plugins.rst15
1 files changed, 0 insertions, 15 deletions
diff --git a/doc/source/hacking/writing_plugins.rst b/doc/source/hacking/writing_plugins.rst
index cecd79053..8425425bf 100644
--- a/doc/source/hacking/writing_plugins.rst
+++ b/doc/source/hacking/writing_plugins.rst
@@ -17,21 +17,6 @@ documentation of your plugin automatically.
Whenever adding a new plugin, you must add an entry for it in ``doc/source/core_plugins.rst``.
-Bump format version
-~~~~~~~~~~~~~~~~~~~
-In order for projects to assert that they have a new enough version
-of BuildStream to use the new plugin, the ``BST_FORMAT_VERSION`` must
-be incremented in the ``_versions.py`` file.
-
-Remember to include in your plugin's main documentation, the format
-version in which the plugin was introduced, using the standard annotation
-which we use throughout the documentation, e.g.::
-
- .. note::
-
- The ``foo`` plugin is available since :ref:`format version 16 <project_format_version>`
-
-
Add tests
~~~~~~~~~
Needless to say, all new feature additions need to be tested. For ``Element``