Skip to content

CD Section Direction Updates : June

Introduction

After each release it's important to update your category and stage visions to ensure they accurately reflect what was delivered, especially in the What's Next sections. You should also consider this an opportunity to make any updates that you might have been considering but not put the time into creating an MR for. Consider creating a branch and reviewing each of your Direction pages (Stage and Categories) one-by-one looking for updates.

Be sure to follow the most up-to-date guidance in the handbook about managing your product direction.

Check the product development timeline for the due date for this content.

Tasks

Submit and merge MRs for any needed updates. If there are updates, post them in the appropriate channels (#s_, #g_)

⭕ Opening Tasks

🔭 Update Group Categories and Related Themes

For example the direction/verify/continous_integration or direction/monitor/health/incident_management pages.

Note: Before submitting for review or merging yourself, be sure to:

  • Consider whether you can separate out controversial and non-controversial updates to focus discussion and feedback on specific changes
  • Look at your page in the review app to make sure that it looks like you expect and you don't have markdown errors
  • Run a spell check and/or grammar checker
  • Open all your links and make sure none go to issues you've already delivered/moved or are otherwise dead links
  • Review and update the entire document, not just the what's next section
  • For controversial or material updates ping your Stage, Section and Product Leaders to provide a global perspective during review
  • @nagyv-gitlab - Deploy:Environments - Category visions reviewed

📈 Review Maturity Plans

Check each category is listed and up to date on the Maturity page. Category Maturity Plans can be updated by modifying categories.yml.

Reminder: changes to Maturity Plans require review!

🕹 Record New Speed Runs

✍ Update Stage Content

Review stage direction pages including tiering strategy content. Be sure to incorporate appropriate pricing themes in that review. On a quarterly basis consider scheduling a Direction review discussion with Product leaders to solicit a global perspective on your stage Direction.

Update Section Content

Review and update section direction pages including tiering strategy content, update section walk-through

  • @nagyv-gitlab - Update Section Direction page
  • @nagyv-gitlab - Update Section Walk Through
  • @nagyv-gitlab - Quarterly - consider scheduling a section-wide direction review and encouraging all Gitlab team members to contribute

Update Exciting Things and Accomplishments (Experimental within the Ops Section)

Consider updating your Exciting Things and Accomplishments sections of your group handbook pages. Consider maintaining no more than three months worth of accomplishments.

  • @nagyv-gitlab - Deploy:Environments - Group handbook page updated

❌ Closing Tasks

FYI - @rayana @mvanremmerden

/ @nagyv-gitlab @mflouton