@@ -29,16 +29,11 @@ The process to release a new version is:
29
29
4 . Commit the changes and tag the commit like ` v1.0.0 ` .
30
30
5 . ` git push --tags origin master `
31
31
6 . Wait for Travis to run, then find and download the binary and Debian
32
- packages for amd64, ppc64el, and arm64 ; there will be links printed at the
32
+ packages for all architectures ; there will be links printed at the
33
33
end of the Travis output. Put these into your ` dist ` directory.
34
- 7 . Wait for the s390x build to run on [ OSU OSL's ibmz-ci
35
- Jenkins server] ( https://ibmz-ci.osuosl.org/job/dumb-init/ ) . This should
36
- happen automatically within 5 minutes of pushing and produce two artifacts
37
- (a binary and a Debian package). Download these into your ` dist ` directory,
38
- similar to the artifacts from Travis.
39
- 8 . Run ` make release `
40
- 9 . Run ` twine upload --skip-existing dist/*.tar.gz dist/*.whl ` to upload the
34
+ 7 . Run ` make release `
35
+ 8 . Run ` twine upload --skip-existing dist/*.tar.gz dist/*.whl ` to upload the
41
36
new version to PyPI
42
- 10 . Upload the resulting Debian packages, binaries, and sha256sums file (all
43
- inside the ` dist ` directory) to a new [ GitHub
44
- release] ( https://github.com/Yelp/dumb-init/releases )
37
+ 9 . Upload the resulting Debian packages, binaries, and sha256sums file (all
38
+ inside the ` dist ` directory) to a new [ GitHub
39
+ release] ( https://github.com/Yelp/dumb-init/releases )
0 commit comments