Re: ostree v2020.1
- From: Alex Kiernan <alex kiernan gmail com>
- To: Colin Walters <walters verbum org>
- Cc: ostree-list <ostree-list gnome org>
- Subject: Re: ostree v2020.1
- Date: Thu, 20 Feb 2020 22:16:00 +0000
On Thu, Feb 20, 2020 at 8:21 PM Colin Walters <walters verbum org> wrote:
https://github.com/ostreedev/ostree/releases/tag/v2020.1
Looks like is_release_build didn't get flipped correctly...
diff --git a/configure.ac b/configure.ac
index a28172a10dea..4824e7c04956 100644
--- a/configure.ac
+++ b/configure.ac
@@ -2,12 +2,12 @@ AC_PREREQ([2.63])
dnl To do a release: follow the instructions to update
libostree-released.sym from
dnl libostree-devel.sym, update the checksum in test-symbols.sh, set
is_release_build=yes
dnl below. Then make another post-release commit to bump the version and set
-dnl is_release_build=no.
+dnl is_release_build=yes
dnl Seed the release notes with `git-shortlog-with-prs
<previous-release>..`. Then use
dnl `git-evtag` to create the tag and push it. Finally, create a
GitHub release and attach
dnl the tarball from `make dist`.
-m4_define([year_version], [2019])
-m4_define([release_version], [7])
+m4_define([year_version], [2020])
+m4_define([release_version], [1])
m4_define([package_version], [year_version.release_version])
AC_INIT([libostree], [package_version], [walters verbum org])
is_release_build=no
It's the commented version that's got picked up, not the uncommented one :|
But it confused the heck out of me for a bit!
--
Alex Kiernan
[
Date Prev][
Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]