aboutsummaryrefslogtreecommitdiff
path: root/sway/ipc-json.c
diff options
context:
space:
mode:
authorSimon Ser <contact@emersion.fr>2021-12-23 14:58:51 +0100
committerSimon Ser <contact@emersion.fr>2021-12-23 19:08:59 +0100
commiteaeb173a4b9b22d8ba1b35d3d863f0dcb8595341 (patch)
tree920c27dccfcb9f7b962bc150a4d67fde7b9aaf7b /sway/ipc-json.c
parent59aebaa5f9f3afe9cdfbb0d37c4dc631690da3b9 (diff)
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.
Diffstat (limited to 'sway/ipc-json.c')
0 files changed, 0 insertions, 0 deletions