15.6 Runner Group iteration plan

The details in this issue cover the top priority work items for the Runner team for the 15.6 release.

Kickoff Video

🟢 15.6 Iteration Planning Schedule

  • Sept 22: PM identifies the candidate features for Runner Core 15.6. It is **not **required that the issue include a proposed solution or implementation plan. @DarrenEastman
  • Sept 22: QA validates candidate bugs for Runner Core 15.6. @zeffmorgan
  • Sept 29: Engineering starts refining issues in the 15.6 iteration plan. @erushton
  • Oct 6: EM Ready to prioritize maintenance work @erushton
  • Oct 12: Refinement - all issues have a proposal or proposed solution. This also includes a response/counter to the “size” of the list (what we think we can commit to, what needs to get pushed out) - first draft.
  • Oct 14: Refinement due - with iteration allowing for any carryover from prior milestone - lock in our “say” for the say/do ratio.
  • Oct 14: Assign issues to developers. @erushton
  • Oct 15: 15.6 PM & design lead records the Runner group kickoff video. @DarrenEastman @gdoyle
  • Oct 24: Start work on 15.6
  • Nov 17: Code freeze 15.6. Calculate the say/do ratio.
  • Nov 22: Ship 15.6.

Forced Prioritization + FedRamp

The top priority in each iteration plan is first to 100% resolve any issues in this list:

Runner Core 🏃

Bugs 🐛

Features

Maintenance 🏚

  • gitlab-org/gitlab#375814+
  • gitlab-org/gitlab-runner#29155+

R&D 🤔

Runner SaaS

15.6 is the final iteration plan that includes the Runner SaaS category. Runner SaaS iteration plans are now tracked in separate issues.

Maintenance 🏚

Runner Fleet 🎢

Bugs

Theme: General Usability Enhancements

Theme: Bulk Deletion

Theme: Runner Queue Visibility

Maintenance

User Experience ✈ 🖌

Edited by Elliot Rushton