From 2cc06ce89a7b60602f3b62487f509ddd40181eb4 Mon Sep 17 00:00:00 2001 From: Jonathan Lebon Date: Fri, 23 Nov 2018 08:55:09 -0500 Subject: [PATCH] configure.ac: Add "GitHub release" step to release workflow Let's make use of the GitHub release feature to make it more prominent on the "Releases" tab, but more importantly so that we can attach vendored tarballs for downstreams. E.g. this will allow us to have a correct `Source0` field in the Fedora spec file. Related: #1683 Closes: #1684 Approved by: rfairley --- configure.ac | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index ef2ab0a7..6c189bfa 100644 --- a/configure.ac +++ b/configure.ac @@ -5,7 +5,9 @@ dnl Then draft release notes highlighting changes and generate the shortlog usin dnl . dnl Then use to create a signed tag with the dnl release notes as its content. -dnl Then, git push origin v201X.XX +dnl Then git push origin v201X.XX. +dnl Then create the xz tarball from `make -f Makefile.dist-packaging dist-snapshot`. +dnl Then create a GitHub release for the new release tag and attach the tarball. m4_define([year_version], [2018]) m4_define([release_version], [9]) m4_define([package_version], [year_version.release_version])