ABCDEFGHIJKLM
1
Rucio 38 retrospective, 2025-07-31
2
Aim of this retrospective is to look back at the 38 Rucio release and evaluate what went well, what should be improved and which actions we will take to
do so. The focus is on the processes: roadmap planning, weekly tracking and followup, differ from the goals, difficulties to identify the objectives, testing,
reviewing, etc.

Specifically look on elements associated with the previous 34 release process, but this is also open to other project improvements.
3
4
I likeI wishWe will
5
be able to run all CI tests locallyto have more informative logs for various exception casesBe able to run all CI tests locally
Side comment: Can be done with https://github.com/nektos/act already		To have more informative logs for various exception cases: Needs tickets on these casesA clearer picture of the dependencies between components (which component relies on what?)
-> Split into packages with pyproject files might help
6
Better tracking of tasks via sprintsA clearer picture of the dependencies between components (which component relies on what?)

+1		Debug daemons using the dev environment [Inserting breakpoints, inspection of code, etc.]Even more people could merge approved prsMore automation in our PR reviews (Closing of stale/unanswered PRs etc.)
7
The sprint structure - it makes it easier to allocate my time across the weeksDebug daemons using the dev environmentWe could close stale issues to decrease the backlog --> Need to look into that
8
More people reviewing (and merging) PRsEven more people could merge approved prs
9
Setting up Rucio/Docu development environments is getting faster/easier
10
The work happening on the CIwe could close stale issues to decrease the backlogMore automation in our PR reviews (Closing of stale/unanswered PRs etc.)
11
12