10.10.2023 Release V8.1.0
Attendees: @James Friel @James Sutherland (Staff) @Ross Teviotdale (Staff) @Susan K
What was the goal?
Release RDMP v8.1.0 with improved performance, managed (scheduled and controlled) and timely release .Engage with Stakeholders around release cycle.
(Late addition) smooth transition of ownership and process.
Did you achieve what you set out to do?
Did the project fully solve the problem it was designed to address?
Did we improve performance? yes
Managed release? Ish
Delays in releasing
Large weakness is lack of performance related testing
no benchmarking
no release pipeline
What lessons did we learn that we can apply to future projects (next section)?
Should do more interim releases?
Better approach to releases - auto numbered betas? More aggressive patch releases?
more managed releases, makes idenitfiy when a bug is released easier
Lessons learnt for more effective future projects
What went well and what should we keep doing?
Having a team
Involving the Software team
Proper look at the UI - improvements, and long-term look
managed release process was useful
large amount of improvements (is a bit hidden)
What could have been improved or what should we stop doing?
Data team interactions
EPCC deployments - MSI packaging?
frequency - minimum once a quarter
In hindsight, what were the risks we didn’t see coming?
8 months to replace Thomas - 3 rounds of recruitment -not suitable candidates
Recruitment in general
Small team size (bus factor) - need to distribute the knowledge
RDMP being a legacy project - all dependencies are old, may just stop working.
insufficient handover(s)
unexpected quirks/hardcoding that are sub-optimal (inefficient, should be in mainline)
1 off hacks for specific projects, don’t go back to mop them up
How do we improve as a team?
backfill documentation as we go through it
-i.e. cohorts -normal rdmp users & how hic wants it to work, how it actually works in HIC due to Jira not working
pipeline for moving one-time hacks to mainline code