|
| 1 | +--- |
| 2 | +name: Release |
| 3 | +about: Checklist and communication channel for PyPI and GitHub release |
| 4 | +title: "Ready for <version-number> PyPI/GitHub release" |
| 5 | +labels: "release" |
| 6 | +assignees: "" |
| 7 | +--- |
| 8 | + |
| 9 | +### PyPI/GitHub rc-release preparation checklist: |
| 10 | + |
| 11 | +- [ ] All PRs/issues attached to the release are merged. |
| 12 | +- [ ] All the badges on the README are passing. |
| 13 | +- [ ] License information is verified as correct. If you are unsure, please comment below. |
| 14 | +- [ ] Locally rendered documentation contains all appropriate pages, including API references (check no modules are |
| 15 | + missing), tutorials, and other human-written text is up-to-date with any changes in the code. |
| 16 | +- [ ] Installation instructions in the README, documentation, and the website (e.g., diffpy.org) are updated. |
| 17 | +- [ ] Successfully run any tutorial examples or do functional testing with the latest Python version. |
| 18 | +- [ ] Grammar and writing quality are checked (no typos). |
| 19 | +- [ ] Install `pip install build twine`, run `python -m build` and `twine check dist/*` to ensure that the package can be built and is correctly formatted for PyPI release. |
| 20 | + |
| 21 | +Please mention @sbillinge here when you are ready for PyPI/GitHub release. Include any additional comments necessary, such as version information and details about the pre-release here: |
| 22 | + |
| 23 | +### PyPI/GitHub full-release preparation checklist: |
| 24 | + |
| 25 | +- [ ] Create a new conda environment and install the rc from PyPI (`pip install <package-name>==??`) |
| 26 | +- [ ] License information on PyPI is correct. |
| 27 | +- [ ] Docs are deployed successfully to `https://www.diffpy.org/<package-name>`. |
| 28 | +- [ ] Successfully run all tests, tutorial examples or do functional testing. |
| 29 | + |
| 30 | +Please let @sbillinge know that all checks are done and the package is ready for full release. |
| 31 | + |
| 32 | +### conda-forge release preparation checklist: |
| 33 | + |
| 34 | +<!-- After @sbillinge releases the PyPI package, please check the following when creating a PR for conda-forge release.--> |
| 35 | + |
| 36 | +- [ ] Ensure that the full release has appeared on PyPI successfully. |
| 37 | +- [ ] New package dependencies listed in `conda.txt` and `test.txt` are added to `meta.yaml` in the feedstock. |
| 38 | +- [ ] Close any open issues on the feedstock. Reach out to @bobleesj if you have questions. |
| 39 | +- [ ] Tag @sbillinge and @bobleesj for conda-forge release. |
| 40 | + |
| 41 | +### Post-release checklist |
| 42 | + |
| 43 | +<!-- Before closing this issue, please complete the following: --> |
| 44 | + |
| 45 | +- [ ] Run tutorial examples and conduct functional testing using the installation guide in the README. Attach screenshots/results as comments. |
| 46 | +- [ ] Documentation (README, tutorials, API references, and websites) is deployed without broken links or missing figures. |
0 commit comments