Source Code Planning 15.6
Overview
| Event | Date |
|---|---|
| Release Start Date | 10/18/2022 |
| Feature Freeze | 11/17/2022 |
| Release Date | 10/22/2022 |
| Milestone Workdays | 21 |
| Deliverable Weight Budget |
Boards
Key Themes
Features typefeature
MVP: view source code rules organized by branches
-
Deliverable slipped %15.5 - Add branch rules details to the list of branch rules 2 frontend backend -
Deliverable slipped %15.5 - Branch rules MVC: Display branch rules details 2 frontend backend
Supporting cross-company goal
-
Deliverable %15.6 - SCM metrics to be instrumented to support our customers and GitLab TAMs in understand product adoption phase 1
Highly demanded features
-
Deliverable %15.6 - Branch and tag with same name cause multiple problems - this is interpreted as a typebug as we do not use git in the correct way.
- very painful for 5 big customers
- Depending on the exact need it may be solve-able by Allow more powerful regexes for protected refs (branches and tags) just below.
- frontend and backend
- backend-weight3 frontend-weight2
- The solution seems to be rather clear. A call with one of the customers to validate the solution is outstanding.
-
Deliverable %15.6 - Configure default branch name for branches created from merge request - 92 upvotes / 4 paying customers
- competition offers this
- needs a little design work to be ready for dev.
- won't be too challenging technically
- decide: do we want to implement this although it contradicts convention over configuration
- relates to: gitlab#16080 (comment 1014196798)+ with 109 upvotes.
-
Deliverable %15.6 Ability to update access levels from Protected Branch API 2 backend - 24 upvotes
UX improvements
-
Deliverable %15.4 will likely slip to %15.5 - Add ability to link to a line on File Blame page 2 frontend UX
Faster syntax highlighting using Highlight.js
(only remaining work is listed)
-
EPIC: Link to package managers when viewing dependency files with highlight.js frontend - This is not a very high priority. When we have capacity in the frontend team we will add one or two of these issues per milestone picking from the top of this child issues list until we are done.
Bugs typebug
Maintenance typemaintenance
Team Capacity
- Total Weight Capacity: TODO
- FE Weight: TODO
- BE Weight: 63
Planning - Planning Board
Product manager prepares the planning with proposed issues for the milestone. Engineering reviews and make recommendations based engineering allocation and capacity.
Checklist
Frontend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month -
Obtain weights for proposed issues -
Recommend issues via engineering allocation as applicable -
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 -
Obtain weights for proposed issues -
Recommend issues via engineering allocation as applicable -
Assign Deliverable Items for Milestone
Product Manager
-
Define Key Themes -
Prepare planning board and submit it for initial capacity assessment and review -
Signs off on final plan
Stable counterparts
-
Technical Writing (@aqualls)
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.
)This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.