-
Notifications
You must be signed in to change notification settings - Fork 307
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
"Brown paper bag" release that actually sets the `is_release_build=yes` flag and also fixes the `Since:` on a few new functions.
- Loading branch information
Showing
3 changed files
with
5 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,15 +2,15 @@ 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], [2020]) | ||
m4_define([release_version], [2]) | ||
m4_define([package_version], [year_version.release_version]) | ||
AC_INIT([libostree], [package_version], [[email protected]]) | ||
is_release_build=no | ||
is_release_build=yes | ||
AC_CONFIG_HEADER([config.h]) | ||
AC_CONFIG_MACRO_DIR([buildutil]) | ||
AC_CONFIG_AUX_DIR([build-aux]) | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters