Prepare for barectf v3.2.0

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Change-Id: Idcb27a5c81a08915278f4d12afb7ac4bdca3a836

diff --git a/README.adoc b/README.adoc
index c09468f06e39eb99bf884a04a494268445d2eda8..ea7a17a93936648aa6c74cd0e4907c235ab1ce2d 100644 (file)
--- a/README.adoc
+++ b/README.adoc
@@ -1,7 +1,5 @@
 // Render with Asciidoctor
 
-:version: 3.1
-
 ifndef::env-github[]
 :toc: left
 endif::env-github[]
@@ -13,7 +11,7 @@ Philippe Proulx
 image::https://barectf.org/barectf-logo.svg[{nbsp}]
 
 https://pypi.python.org/pypi/barectf[image:https://img.shields.io/pypi/v/barectf.svg[]]
-https://ci.lttng.org/job/barectf_stable-{version}_build[image:https://img.shields.io/jenkins/s/https/ci.lttng.org/barectf_stable-{version}_build.svg[]]
+https://ci.lttng.org/job/barectf_master_linuxbuild[image:https://img.shields.io/jenkins/s/https/ci.lttng.org/barectf_master_linuxbuild.svg[]]
 
 [.lead]
 https://barectf.org/[**_barectf_**] (from _bare_ metal and _CTF_)
@@ -26,13 +24,13 @@ https://diamon.org/ctf/[CTF] data streams.
 This README mostly documents barectf development.
 
 To learn how to use barectf, read its
-https://barectf.org/docs/barectf/{version}/[documentation].
+https://barectf.org/docs/barectf/[documentation].
 ====
 
 == Install barectf
 
 See the barectf documentation's
-https://barectf.org/docs/barectf/{version}/install.html[Install barectf]
+https://barectf.org/docs/barectf/3.1/install.html[Install barectf]
 page.
 
 == Build barectf
@@ -58,8 +56,7 @@ https://docs.antora.org/antora/latest/component-version/[Antora
 documentation component version] under the `docs` directory.
 
 This component version is the source of the
-https://barectf.org/docs/{version}/[barectf documentation website]
-(version{nbsp}{version}).
+https://barectf.org/docs/[barectf documentation website].
 
 You can refer to this component version in your
 https://docs.antora.org/antora/latest/playbook/[Antora playbook file],
@@ -107,5 +104,4 @@ $ tox
 == Get help
 
 See the barectf documentation's
-https://barectf.org/docs/barectf/{version}/get-help.html[Get help]
-page.
+https://barectf.org/docs/barectf/3.1/get-help.html[Get help] page.

diff --git a/barectf/version.py b/barectf/version.py
index b6ba0257f7cc6838e70b873bafbb12d78f95ce2f..eb026213a075b5318c4b6c90ea918352596a2502 100644 (file)
--- a/barectf/version.py
+++ b/barectf/version.py
@@ -22,7 +22,7 @@
 # SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 __major_version__ = 3
-__minor_version__ = 1
+__minor_version__ = 2
 __patch_version__ = 0
-__pre_version__ = ''
+__pre_version__ = '-dev'
 __version__ = f'{__major_version__}.{__minor_version__}.{__patch_version__}{__pre_version__}'

diff --git a/docs/antora.yml b/docs/antora.yml
index 18c34a8d45f1f036345a4ee4a40d29493ffd5a9a..b97af023ab5e0446d1a700fab32f1b5040cdbff9 100644 (file)
--- a/docs/antora.yml
+++ b/docs/antora.yml
@@ -1,6 +1,6 @@
 name: barectf
 title: barectf
-version: '3.1'
+version: '3.2'
 asciidoc:
   attributes:
     req-abbr: '<abbr title="Required?">Req?</abbr>'

diff --git a/docs/modules/ROOT/pages/whats-new.adoc b/docs/modules/ROOT/pages/whats-new.adoc
index 41fe266dfec5ba63fd5b28ae9af8def201f91ff4..8aa85204ae9c866afa4622315f8b6a5f05432f12 100644 (file)
--- a/docs/modules/ROOT/pages/whats-new.adoc
+++ b/docs/modules/ROOT/pages/whats-new.adoc
@@ -1,32 +1,3 @@
 = What's new in barectf{nbsp}{page-component-display-version}?
 
-Thanks to a https://review.lttng.org/c/barectf/+/7496[contribution from
-Jon Lamb], the xref:how-barectf-works:ctf-primer.adoc#pkt[CTF packets]
-which a barectf-generated tracer writes can contain an
-automatically-incremented **sequence number** in their context field.
-This is useful for a trace reader/analyzer to detect packets lost at
-transport time, for example. https://babeltrace.org/[Babeltrace{nbsp}2]
-supports such a packet context field out of the box.
-
-To enable this new packet feature, set the
-xref:yaml:dst-obj.adoc#seq-num-ft-prop[`sequence-number-field-type`
-property] of the packet features object, for example:
-
-.Data stream type object with an enabled packet sequence number field type feature.
-====
-[source,yaml]
-----
-$features:
-  packet:
-    sequence-number-field-type: true
-event-record-types:
-  # ...
-----
-====
-
-This feature is disabled (false) by default to avoid breaking changes.
-
-The xref:platform:api.adoc#close[packet closing function] automatically
-increments the current packet sequence number of the barectf context.
-Within platform code, you can get the current value with
-xref:platform:api.adoc#barectf-pkt-seq-num-func[`barectf_packet_sequence_number()`].
+TODO!

diff --git a/pyproject.toml b/pyproject.toml
index afa294fe875a0070da96cf6342f6207159558c67..1e78180587615e2585d4220101c89b152d602bba 100644 (file)
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -27,7 +27,7 @@ build-backend = 'poetry.core.masonry.api'
 
 [tool.poetry]
 name = 'barectf'
-version = '3.1.0'
+version = '3.2.0-dev'
 description = 'Generator of ANSI C tracers which output CTF data streams'
 license = 'MIT'
 authors = ['Philippe Proulx <eeppeliteloop@gmail.com>']