From: Tom Hromatka Date: Fri, 10 Jan 2020 21:13:10 +0000 (-0700) Subject: doc: Add release process for github X-Git-Tag: v0.42~2^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b6e6e96bd872e44a27555605c287dc41a5a5e459;p=thirdparty%2Flibcgroup.git doc: Add release process for github Signed-off-by: Tom Hromatka --- diff --git a/doc/internal/release-github.txt b/doc/internal/release-github.txt new file mode 100644 index 00000000..f7e59dd9 --- /dev/null +++ b/doc/internal/release-github.txt @@ -0,0 +1,25 @@ +1. Update version in configure.in + a. AC_INIT([libcgroup],[0.XX]) + b. Add an .rcY to the end, e.g. 0.XX.rcY +2. Build + a. Run ./bootstrap.sh + b. Run ./configure + c. Run make check + d. Run make dist +3. Tag the Release + a. git tag -s -a -m "v0.XX.rcY" v0.XX.rcY +4. Push to github + a. git push origin v0.XX.rcY + b. Generate a checksum for the *.tar.gz and *.tar.bz2 and ... + sha256sum > libseccomp-X.Y.Z.tar.gz.SHA256SUM + c. Upload the zips and checksums to the github release + d. Email libcg-devel about the new release w/ the changelog + git shortlog v0.XX.rc(Y-1)..v0.XX.rcY +5. Verify continuous integration passes + a. Verify TravisCI, code coverage, etc. all pass + b. If the CI checks fail, fix it, and go back to step #1 +6. Fix issues identified as critical for current rc(Y+1) + a. If any issues fixed, update the rcY number and go to step #1 + b. If no issues, go to step #7 +7. Release Notes +8. Do steps #1 through #5 (except step #1b)