MRenvoize/QA Manager

Proposal

I propose to be the QA Manager for the 24.11 cycle.

24.11

I want to try and drive more adoption of the dashboard for managing the quality assurance queues, refining the ToDo lists to our agreed priorities taking into account the different keywords like rm_priority, rel_candidate and roadmap as well as reconsidering the approach of listing 'oldest' bugs in each category...

I'd like us to focus on 'most recently worked on + oldest reported' as a sorting algorithm.

Finally, I want to try and promote more 'working together', bringing developers together at same time to focus on particular topic area's in sprints.