Create a checklist to ensure all tests can pass in MONAI repos before the release #6603
Replies: 3 comments 5 replies
-
If you can reduce the commits between final release candidate and final version that would minimize the issues. Earlier we were trying to keep the gap between release candidate and final version very small. That will help to discover any issues immediately |
Beta Was this translation helpful? Give feedback.
-
For the some of the codebase the code coverage report provides some info, like this https://app.codecov.io/gh/Project-MONAI/MONAI Maybe we can generate some logs for each repo to indicate the test coverage.. not sure how to do it for notebooks, perhaps per file based instead of per line or per cell... |
Beta Was this translation helpful? Give feedback.
-
Hi @wyli I saw you maintained this checklist for every release. Is it appropiate to add the items I mentioned above into the checklist for future versions as well? |
Beta Was this translation helpful? Give feedback.
-
MONAI 1.2 is released recently, and after the release, this bug immediately emerged from MONAILabel unittest because I did not run all the unit and integration tests.
To improve our workflow and avoid this from happening again, I suggest we create a checklist (Google sheet), or create the milestone on GitHub to ensure all checks are done by PICs before the release. A few items to include are:
cc @wyli @Nic-Ma @yiheng-wang-nv @tangy5 @SachidanandAlle
Beta Was this translation helpful? Give feedback.
All reactions