Add templates for PR and Release

.github/ISSUE_TEMPLATE/release_checklist.md

@@ -0,0 +1,43 @@
+---
+name: Release checklist
+about: Ensure the project is ready to make a release.
+title: Release Checklist v?.?.?
+labels: ''
+assignees: ''
+
+---
+
+*This release checklist is intended to help keep to a consistent process for minor version releases.*
+*The same process may be used for point releases, though usually with compressed timescales.*
+
+*Minor version releases will generally be made from the `main` branch.*
+*Bugfix releases may be made either from `main` or from a protected `v0.x` branch depending on whether there are significant changes already merged onto `main`.*
+
+**Start of cycle**
+- [ ] Create a milestone for the release.
+- Add issues and pull requests to the release.
+
+**Development**
+- Open pull requests to close issues, prioritising those tagged for the next release.
+- Periodically review priorities, usually with a subset of the OpenFlexure team.
+
+**Release preparation**
+- [ ] Decide on issues and PRs that will be included, adjusting milestones as necessary.
+- [ ] Make a prerelease on PyPI for testing.
+
+**Testing**
+- [ ] Check that all formatting, linting, unit, and integration tests are passing on CI
+- [ ] Verify core functionality against a real system:
+    - [ ] Run a large ( > 200 images) slide scan on an OpenFlexure Microscope
+    - [ ] Verify the UI on the OpenFlexure Microscope works as expected
+    - [ ] Report any relevant bugs as an Issue in the [OpenFlexure Microscope Server Repository](https://gitlab.com/openflexure/openflexure-microscope-server)
+- [ ] Open issues and PRs in the labthings-fastapi to fix any bugs that are found in the labthings software.
+
+**Release**
+- [ ] Bump the version number in `pyproject.toml`
+- [ ] Make a release on Github, including a changelog in the release notes.
+- [ ] Verify that the release appears on PyPI and add a link to the Github release.
+
+**Post-Release**
+- [ ] Announce the new release on relevant channels, including telling the OpenFlexure Core Team and other other downstream project teams.
+- [ ] Close this issue and the corresponding GitHub Milestone.

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,42 @@
+---
+name: Pull request
+about: Proposed changes to the software.
+title: ''
+labels: ''
+assignees: ''
+---
+
+**REPLACE ME** with a short summary of the context for this merge request.
+<!-- Add summary of what this MR does above this comment -->
+
+<!-- Closes #???-->
+<!-- OFM-Feature-Branch: branchname -->
+
+## This MR contains the following
+* Bulleted
+* Description of changes
+
+<!-- uncomment if there are things to finish before merge
+## Before merge:
+
+* [ ] Remaining thing 1
+* [ ] Remaining thing 2
+-->
+
+
+## Merge checklist:
+<!-- Do not remove irrelevant checklist items.-->
+<!-- Use ~strikeout~ to strike out not applicable questions, removing the [ ] so that the checklist count is correct.-->
+
+* [ ] All new/changed functions have up to date typehints and docstrings.
+* [ ] Any changes to the public API have been updated in `docs/src/public_api.rst`.
+* [ ] New or changed features have been added to (or updated in) the conceptual documentation.
+* [ ] Any new or updated dependencies have been added to the project configuration (e.g., `pyproject.toml`).
+* [ ] New functionality is fully tested.
+* [ ] Any decrease in test coverage has been justified.
+* [ ] Either the `test-against-ofm-v3` job passes, or `test-against-ofm-feature-branch` passes.
+* [ ] New features have been used in a branch of the OpenFlexure Microscope, which is tested in `test-against-ofm-feature-branch`.
+      <!-- Note: uncomment the `OFM-Feature-Branch: branchname` line above to test against a feature branch in CI. -->
+* [ ] This code has been tested manually against simulated hardware (detail tests in "Before merge").
+* [ ] This code has been tested against real hardware (detail tests in "Before merge").
+