@lma-git that's perfect, this is an overdue corrective action. Thank you!
@pedropombeiro good call, and agreed those shouldn't impact the stats.
To clarify, I didn't remove all Stretch issues from the milestone. There are still Stretch issues in 18.11. I only moved a couple of CI/CD analytics group-level issues to 19.0 since they were suggested as Stretch during planning and are also blocked by other issues. We can always pull them back if needed.
My main takeaway is that even without counting the remaining Stretch issues, the milestone looks fully planned with committed work.
This is roughly the same number of issues compared to the previous milestone (29 vs 28), but the weight comparison is less straightforward since 18.10 had 7 issues with no weights versus zero in 18.11. With all issues now weighted, our committed total of 63 weights gives us better visibility into the actual scope.
A few notes on the current state:
Tracking issue is now updated.
cc @gitlab-com/ci-platform-group
We closed 18.10 with:
We opened 18.11 with:
We have carried over 11 issues (total weight of 32) - in previous calculations I made a mistake.
I moved it to blocked until we ensure the above fix is shipped and work as expected.