NeonXP/dumb-init
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Remove s390x instructions from CONTRIBUTING

Browse source
This commit is contained in:
Chris Kuehl 2019-12-04 10:18:20 -08:00
parent 8b24bad35c
commit bcb22abff5
1 changed files with 6 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
CONTRIBUTING.md
View file

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