aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Simon Ser <contact@emersion.fr>2021-12-23 14:58:51 +0100
committerLibravatar Simon Ser <contact@emersion.fr>2021-12-23 19:08:59 +0100
commiteaeb173a4b9b22d8ba1b35d3d863f0dcb8595341 (patch)
tree920c27dccfcb9f7b962bc150a4d67fde7b9aaf7b
parentAdd cairo_image_surface_create error handling (diff)
downloadsway-eaeb173a4b9b22d8ba1b35d3d863f0dcb8595341.tar.gz
sway-eaeb173a4b9b22d8ba1b35d3d863f0dcb8595341.tar.zst
sway-eaeb173a4b9b22d8ba1b35d3d863f0dcb8595341.zip
build: bump version to 1.8-dev
Historically we've been sticking with the last release number in the master branch. However that's a bit confusing, people can't easily figure out whether they're using a release or a work-in-progress snapshot. Only the commit hash appended to the version number may help, but that's not very explicit and disappears when using a tarball. We could bump the version in master to the next release number. However during the RC cycle there would be a downgrade from 1.8 to 1.8-rc1. Also it would be hard to tell the difference between a stable release and an old snapshot. This patch introduces a new pre-release identifier, "dev". It's alphabetically before "rc" so it should be correctly sorted by semver comparisons. "dev" is upgraded to "rc" (and then to stable) when doing a release. The master branch always uses a "dev" version, only release branches use "rc" or stable versions.
-rw-r--r--meson.build2
1 files changed, 1 insertions, 1 deletions
diff --git a/meson.build b/meson.build
index 2a271d36..4da9403b 100644
--- a/meson.build
+++ b/meson.build
@@ -1,7 +1,7 @@
1project( 1project(
2 'sway', 2 'sway',
3 'c', 3 'c',
4 version: '1.6', 4 version: '1.8-dev',
5 license: 'MIT', 5 license: 'MIT',
6 meson_version: '>=0.60.0', 6 meson_version: '>=0.60.0',
7 default_options: [ 7 default_options: [