|
1 | 1 | # Making a backup-utils release
|
2 | 2 |
|
3 |
| - 1. Install the debian devscripts package: |
4 |
| - `sudo apt-get install devscripts` |
5 |
| - 2. Add a new version and release notes to the `debian/changelog` file: |
6 |
| - `dch --newversion 2.6.0 --release-heuristic log` |
7 |
| - You can use `make pending-prs` to craft the release notes. |
8 |
| - 3. Rev the `share/github-backup-utils/version` file. |
9 |
| - 4. Tag the release: `git tag v2.0.2` |
10 |
| - 5. Build that tarball package: `make dist` |
11 |
| - 6. Build the deb package: `make deb`. All the tests should pass. |
12 |
| - 7. Draft a new release at https://github.com/github/backup-utils/releases, including the release notes and attaching the tarball and deb packages. |
13 |
| - The dist tarball you should upload has the git revision in the file name, i.e. something like `github-backup-utils-v2.5.0.tar.gz` |
14 |
| - 8. Push the head of the release to the 'stable' branch. |
| 3 | +## Automatic Process from chatops (internal to GitHub only) |
| 4 | + |
| 5 | +1. `.ghe backup-utils-release 2.12.0` |
| 6 | + |
| 7 | +## Automatic Process from CLI |
| 8 | + |
| 9 | +1. Install the Debian `devscripts` package: |
| 10 | + `sudo apt-get install devscripts` |
| 11 | +2. Run `GH_AUTHOR="Bob Smith <[email protected]>" GH_RELEASE_TOKEN=your-amazing-secure-token script/release 2.12.0` |
| 12 | + |
| 13 | +## Manual Process |
| 14 | + |
| 15 | +In the event you can't perform the automatic process, or a problem is encountered with the automatic process, these are the manual steps you need to perform for a release. |
| 16 | + |
| 17 | +1. Install the Debian `devscripts` package: |
| 18 | + `sudo apt-get install devscripts` |
| 19 | +2. Add a new version and release notes to the `debian/changelog` file: |
| 20 | + `dch --newversion 2.12.0 --release-heuristic log` |
| 21 | + You can use `make pending-prs` to craft the release notes. |
| 22 | +3. Rev the `share/github-backup-utils/version` file. |
| 23 | +4. Tag the release: `git tag v2.12.0` |
| 24 | +5. Build that tarball package: `make dist` |
| 25 | +6. Build the deb package: `make deb`. All the tests should pass. |
| 26 | +7. Draft a new release at https://github.com/github/backup-utils/releases, including the release notes and attaching the tarball and deb packages. |
| 27 | + The dist tarball you should upload has the revision in the file name, i.e. something like `github-backup-utils-v2.12.0.tar.gz` |
| 28 | +8. Push the head of the release to the 'stable' branch. |
0 commit comments