From ca2528b95bdfa5a8e1d22c58269b7c2b3aa282ba Mon Sep 17 00:00:00 2001 From: Mark Dickinson Date: Mon, 8 Jul 2024 12:16:54 +0100 Subject: [PATCH] Remove the issue template (#355) The issue template for this repository wasn't terribly helpful (the only non-blank-issue option was for a release template), and the only template is now out of date. This PR removes the template (but keeps the PR template that reminds people to add a news entry). Information on making releases is now on the wiki at https://github.com/enthought/apptools/wiki/Releasing. --- .github/ISSUE_TEMPLATE/release_template.md | 68 ---------------------- 1 file changed, 68 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/release_template.md diff --git a/.github/ISSUE_TEMPLATE/release_template.md b/.github/ISSUE_TEMPLATE/release_template.md deleted file mode 100644 index 4a0bd858..00000000 --- a/.github/ISSUE_TEMPLATE/release_template.md +++ /dev/null @@ -1,68 +0,0 @@ ---- -name: (Maintainers only) Release Checklist -about: Use this template for upcoming releases. -title: "[Release Number] Release Checklist" ---- - -Target date: - -Release Candidate by YYYY-MM-DD - -Release by YYYY-MM-DD - -Release candidate -------------------- -- [ ] Verify that all relevant PRs have been merged to ``main``. -- [ ] Create a PR against ``main`` to bump version number, merge that PR -- [ ] From the commit just before bumping the version, create a new branch `maint/` -- [ ] Update changelog and open PR targeting a new `maint/` branch. - To do so, use the `python etstool.py changelog build` command to update the changelog - file. You will still need to review / edit it and also confirm that all news fragments - were included / delete the files. -- [ ] Update `ci-src-requirements.txt` if needed -- [ ] Check MANIFEST and requirements are still up to date. -- [ ] Update version in setup.py for the prerelease, open 2 PRs against `maint/` - - [ ] Create a new branch from `maint/`: `git checkout maint/`; `git pull`; `git checkout -b call-it-anything-you-like` - - [ ] Set `PRERELEASE` to "rc1" and `IS_RELEASED` to true, commit, e.g. `git commit -m "Set IS_RELEASED to true for prerelease rc1"` - - [ ] Open and merge a PR against `maint/` - - [ ] Create a new branch from `maint/`, Flip `IS_RELEASED` back to false, commit. - - [ ] Open and merge another PR against `maint/` -- [ ] Tag (annotated!) the release candidate on the commit where IS_RELEASED is set to true, e.g. `git tag -a -m "Release candidate rc1" rc1 ` -- [ ] Push the tag to GitHub -- [ ] Upload to PyPI - - `git checkout `, `git clean -ffxd`, `python setup.py sdist`, `twine check dist/<...>.tar.gz`, `twine upload dist/<...>.tar.gz` -- [ ] Announcement for the release candidate - -Release blockers ----------------- -- [ ] (add blocking issues/PRs here) - -Pre-release ---- -- [ ] Backport PRs that have been merged to ``main`` to the maintenance branch. Use the "need backport ..." tag if there is one (but don't rely 100% on it) -- [ ] Verify that no other open issue needs to be addressed before the release. -- [ ] Test against other ETS packages and other ETS-using projects -- [ ] Check MANIFEST, requirements, changelog are still up to date. -- [ ] Test building the documentation - -Release -------- -- [ ] Create branch `release/` from `maint/` branch. - - [ ] Set release to ``, and set `IS_RELEASED` is true; commit - - [ ] Install from source distribution and run tests again - - [ ] Open a PR against `maint/` with this being the last commit so that CI is built on the release commit - - [ ] Once CI is done building merge PR - - [ ] Bump the micro version number i.e. `` and set `IS_RELEASED` to false; commit. - - [ ] Open and then merge a separate PR against `maint/` -- [ ] From the commit at which `IS_RELEASED` is true and version is ``, tag (annotated!) `git tag -a -m "Release " ` -- [ ] Push the tag `git push origin ` -- [ ] Make PR targeting `gh-pages` branch: Generate documentation and copy the content to the branch. Verify that the resulting index.html looks good. -- [ ] Upload to PyPI -- [ ] Test the PyPI package - -Post-release -------------- -- [ ] Package update for `enthought/free` repository (for EDM) -- [ ] Backport change log (and any deletion of news fragments) to ``main`` -- [ ] Update GitHub Release pages https://github.com/enthought/apptools/releases -- [ ] Announcement (e.g. Google Group)