Fix "stop using %{release}"

Olf0 · Dec 27, 2019 · 491fa32 · 491fa32
1 parent afbdf21
commit 491fa32
Showing 1 changed file with 9 additions and 2 deletions.
diff --git a/rpm/obexd-contentfilter-off.spec b/rpm/obexd-contentfilter-off.spec
@@ -1,7 +1,14 @@
 Name:          obexd-contentfilter-off
 Summary:       Disable filter for supported MIME types when receiving files per OBEX with bluez
-Version:       1.0
-# Release:      1  # The release number is not used, changes to the spec file bump the bug fix release number (third field)
+Version:       1.1.0
+# Stop evaluating the "Release:" field (per %{release}) and cease including it in git tags since v1.1.0, 
+# in order to satisfy OBS and consequently switching to a three field semantic versioning scheme for
+# releases and their git tags.
+# Hence any changes to the spec file now always trigger an increase of the bug fix release number, i.e.
+# the third field of %{version}.
+# But %{release} is now (ab)used to merely *indicate* the estimated release quality by setting it
+# to {alpha, beta, stable}.  Note that no other identifiers shall be used.
+Release:       stable
 Group:         System/Base
 # Distribution: SailfishOS # , MeeGo and maybe also other descendants of MeeGo
 Vendor:        olf