Source Code Planning 15.11
Release planning for the Source Code Group
Overview
Highlights
- Start working on helping users better understand the CODEOWNERS file format and prevent errors when creating/maintaining CODEOWERS with the goal to make it easier to create and maintain code owners
- Continue to enable E2E workflow for setting branch rules - from discovery to changing the rule with the goal to improve the user experience
- Improving Forking experience for better contribution experience on open source projects and to enable large organizations to keep write access on projects to a minimum.
Details
Planning work
Team Capacity
| Release Start Date | 3/20/2023 |
| Feature Freeze | 4/17/2023 |
| Release Date | 4/22/2023 |
| Milestone Workdays | 21 |
| Deliverable Weight Budget | 10.5 |
| Milestone Weight Budget | 48 |
- Total Weight Capacity: TODO
- FE Weight: TODO
- BE Weight: 48
Planning
- Planning Board - for the entire group
- UX Planning board
- Planning Board - backend
- Planning Board - frontend
Bugs with high customer priority
Sorted from highest priority according to customer priority (top is highest priority)
Bugs with high upvotes
Sorted from highest priority according to customer priority (top is highest priority)
Build Boards
Checklist
Frontend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month -
Propose prioritized list of typemaintenance issues in a comment -
Obtain weights for proposed issues -
Collaborate with product manager to finalize the plan -
Assign Deliverable Items for Milestone
Backend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month -
Propose prioritized list of typemaintenance issues in a comment -
Obtain weights for proposed issues -
Collaborate with product manager to finalize the plan -
Assign Deliverable Items for Milestone
Quality Engineer
-
Propose prioritized list of typebug issues in a comment and request weights from engineering where still necessary
Product Manager
-
Propose prioritized list of typefeature issues in a comment and request weights from engineering where still necessary -
Collaborate with counterparts in engineering to finalize the plan -
When planning is done: remove Draft:from the title -
Document the highlights and label these issues as direction -
Document the entire list of issues -
Create video summarizing the highlights -
Close the plannning issue
Stable counterparts
-
Technical Writing ( @aqualls)
Edited by Sean Carroll