• Closed since last retrospective (April 23)
  • Documentation how to setup an RSE (for newcomers, and best practices) [38 retrospective item]
  • Need to be stricter during ticket review [38]
  • Be able to run all CI tests locally Side comment: Can be done with https://github.com/nektos/act already [38, but duplicate]
  • Even more people could merge approved prs [38]
  • Collect feedback on PR template and Reviewer template and Conventional Commits [40]
  • Investigate how to improve sprint planning [40]
  • RucioBot: Maybe in issue management? [40, rejected]
• In progress
  • A clearer picture of the dependencies between components (which component relies on what?) -> Split into packages with pyproject files might help [38]
  • Add/Clarify merging, code freeze, release logic, to the contribution guide [38]
  • Add review guidelines to the contribution guide (Testcases) [38]
  • Implement a client release test procedure [38]
  • Clarify RSE settings vs. attributes -> Full move to attributes might be difficult [38]
  • Martin to port CERN Onboarding guide to a general onboarding guide and add to documentation [40]
  • Improving tests: Running locally, making tests easier [40]
  • Faster tests: reduce the test suites we run (not all are necessary all the time) [40]
• Not started
  • Debug daemons using the dev environment [Inserting breakpoints, inspection of code, etc.] [38]
  • To have more informative logs for various exception cases: Needs tickets on these cases [38]
  • Investigate ways of introducing reviewers in parts of review [38]
  • Formalise consistency guidelines for adding new RSE attributes, settings, commands, rest endpoints etc. (more discsssuion to follow) [38]
  • Documentation of how the config table vs cfg file works, and when which one should be used. [38]
  • Improve documentation how to setup rucio in a non-k8s environment (Possibly with x509 certificates) [38]
  • Review setup of development environment, make it easier to onboard developers -> have a generic version? [38]
  • Run tests differently based on policy package [39]
  • How could we run integration tests with e.g. hierarchical schemas, dirac, etc. ? [39]
  • Add another person (at least) to merger team [39]
  • Need code coverage strategy [39]
  • Split coverage by unit and intake tests - make it clear to somebody looking at PRs [39]
  • Coverage is currently only based on unittest (not intake) [39]
  • Move tests in the testsuite to the unittest folder [39]
  • See if we can get more people into the WebUI? [40]
  • Mention in the sprint planning that review MUST/SHOULD be part of the sprint [40]
  • Look into GH runners @ CERN to improve faster tests [40]