-
# 🎯 Problem to be solved
We should improve the current release checklist (to fix ahead of tagging the release) according to the comments shared in https://docs.google.com/document/d/1Ku4IQ8EbMNcCVSi4a…
-
- a checklist to print out that contains all things that need to be checked on release would be useful
- The checklist includes manual test cases, git tagging including tag signing, change log update,…
-
# Repo checklist
- [x] data API up-and-running
- [x] unittests imlplemented
- [x] coverage is tracked
- ~[ ] linting for PR implemented~
- [x] documentation up-and-running
# Deployment checkli…
-
After a long planning session due to mainnet ready release of Content Service, conclusions below:
0) We're finishing tasks from previous Iteration.
1) Senior Developers need to discuss scenarios o…
-
- [x] https://github.com/crytic/tealer/issues/1
- [x] https://github.com/crytic/tealer/issues/2
In addition, we should prepare the next release to be ready for `pip` to ease the installation
-
Prepare new release that reflects changes from streaming Our Networks 2019. Here is a checklist:
- [ ] Update text and diagrams on [README](https://github.com/tomeshnet/ipfs-live-streaming/blob/mas…
-
### Description of the bug
There are a couple of things to address before a first release:
- [x] Move all containers to be biocontainers
- [ ] Migrate the code to follow guidelines on nf-core:
…
-
JIRA Issue: [KIEKER-38] Create release notes for Kieker 1.7
Original Reporter: Andre van Hoorn
***
## Checklist:
[KIEKER-38]: https://kieker-monitoring.atlassian.net/browse/KIEKER-38?atlOrigin=ey…
-
# Release Checklist
## Before Release
* [x] Update the checklist Issue template in the [``.github/ISSUE_TEMPLATE``](https://github.com/scikit-hep/pyhf/tree/main/.github/ISSUE_TEMPLATE) directory…
-
With release hardware on the horizon we're ramping up toward a launchable codebase with wrinkles ironed out and a small wishlist of day-1 features:
1. [ ] The blit API should be reasonably stable b…