Skip to content

Commit 00892ab

Browse files
authored
Update the release process
- Drop the custom made tarball: We now rely on [signed git tags](https://gitlab.archlinux.org/archlinux/packaging/packages/archlinux-contrib/-/commit/50905be547cd72eb1bcd1efab5b988e00781b883) for the package, which is more straightforward and transparent. IMO there's no need to keep creating this extra tarball. - Move the whole release process into a single `release` target - Switch to `gh`: `hub` throws an error (not sure if it's broken or expects something missing) - Document the release process in the README
2 parents 1cea355 + e270137 commit 00892ab

File tree

2 files changed

+9
-11
lines changed

2 files changed

+9
-11
lines changed

Makefile

Lines changed: 4 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
PREFIX = /usr/local
22
SHAREDIR = $(PREFIX)/share/archlinux
33
BINDIR = $(PREFIX)/bin
4-
REPO = contrib
5-
TAG = $(shell git describe --abbrev=0 --tags)
64

75
BASH_SCRIPTS = \
86
admin/checkservices \
@@ -37,17 +35,12 @@ uninstall:
3735
done;
3836
rmdir $(DESTDIR)$(BINDIR)
3937

40-
.PHONY: tag
41-
tag:
42-
git describe --exact-match >/dev/null 2>&1 || git tag -s $(shell date +%Y%m%d)
43-
git push --tags
44-
4538
.PHONY: release
4639
release:
47-
mkdir -p releases
48-
git archive --prefix=${REPO}-${TAG}/ -o releases/${REPO}-${TAG}.tar.gz ${TAG};
49-
gpg --detach-sign -o releases/${REPO}-${TAG}.tar.gz.sig releases/${REPO}-${TAG}.tar.gz
50-
hub release create -m "Release: ${TAG}" -a releases/${REPO}-${TAG}.tar.gz.sig -a releases/${REPO}-${TAG}.tar.gz ${TAG}
40+
git describe --exact-match >/dev/null 2>&1 && { echo "Last commit is already tagged" >&2; exit 1; }
41+
git tag -s $(shell date +%Y%m%d)
42+
git push --tags
43+
gh release create --generate-notes $(shell date +%Y%m%d)
5144

5245
check: check-bash check-python
5346

README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,14 @@ years so they can be curated, cleaned up and maybe become part of the `devtools`
77
package.
88

99
### Contribution guidelines
10+
1011
- Some documentation is needed. This can be comments in the top of the file or
1112
a traditional help command.
1213

1314
- One ACK for each Pull-Request is needed
1415

1516
- Please add [SPDX license header](https://spdx.org/ids-how)
17+
18+
### Release process
19+
20+
Run `make release` to push a signed git tag and create a release with default changelog (requires `gh`).

0 commit comments

Comments
 (0)