Speaker:
Martin Barisits
(CERN)
- Actions from 39 retrospective
- Move tests in the testsuite to the unittest folder
- Coverage is currently only based on unittest (not intake)
- Split coverage by unit and intake tests - make it clear to somebody looking at PRs
- Need code coverage strategy
Work on contribution standards, we need to raise the bar to make review easier for the few reviewers- Add another person (at least) to merger team
- How could we run integration tests with e.g. hierarchical schemas, dirac, etc. ?
- Run tests differently based on policy package
- Actions from previous reviews
- 🚧 Clarify RSE settings vs. attributes -> Full move to attributes might be difficult
- 🚧 Implement a client release test procedure
Documentation how to setup an RSE (for newcomers, and best practices)- Formalise consistency guidelines for adding new RSE attributes, settings, commands, rest endpoints etc. (more discsssuion to follow)
- 🚧 Add review guidelines to the contribution guide (Testcases)
- 🚧 Add/Clarify merging, code freeze, release logic, to the contribution guide
Investigate changes to merging policy, code freeze policy, and release logic- 🚧 Need to be stricter during ticket review
- Maybe include the bot to do some assignment/triage work
- We could close stale issues to decrease the backlog --> Need to look into that
- 🚧 A clearer picture of the dependencies between components (which component relies on what?) -> Split into packages with pyproject files might help
- We will work on requirements management first
- 🚧 Even more people could merge approved prs
More automation in our PR reviews (Closing of stale/unanswered PRs etc.)
