Skip to content

Technical Writing milestone plan for 18.2

This issue provides a consolidated view of what the Technical Writing team expects to work on with their assigned groups for the upcoming milestone. In addition to the work with their assigned groups, the Technical Writing team also works on other tasks that are not reflected in this issue.

On the 1st of each month:

The TW Bot creates the issue for the upcoming milestone using a scheduled pipeline and a template.

We open this issue on the 1st to align with planning activities carried out by other teams and stakeholders. The 1st is on or around 12 days before the milestone begins. For example, for 16.8 (2024-01-17), the milestone starts on 2023-12-16 and we open this issue on 2023-12-01. For more information, see the product development timeline.

By the start of the milestone:

The TW carries out planning activities for their assigned groups, and populates Checklist and links to confirm these activities have taken place:

  1. Have a conversation - synchronously or asynchronously - with either the group PM or EM to review:

    • Planned documentation and UI text work for the upcoming milestone (Milestone: Upcoming) or (Milestone: Started).
    • Improvement or development opportunities they're aware of in their areas of the product documentation.
    • If any deprecations can be announced according to the process for deprecations, removals, and breaking changes. Deprecations should be announced as soon as possible, but the group should have a firm idea of deprecated features from about half-way through a major release cycle.

    This can be a regular group meeting or any other means of communication that you have established with your group.

    If the TW, PM, or EM is unavailable around the beginning of the milestone, we encourage using async methods (like commenting in issues or Slack messages) or having conversations at an earlier time. If the conversation happens before the creation of the issue, just add the planning information to the issue when it's available.

  2. Identify a linked artifact that describes the upcoming planned work, such as:

    • An issue board for the group's documentation/UI text items for the milestone.
    • A filter that describes/lists the planned work. (Example for devopsplan)
    • The group's planning issue, if it identifies issues/MRs that require Technical Writing team involvement. (Example)

  3. Select the appropriate checkboxes and share the links to planned features to confirm that the "conversation" has taken place.

Checklist and links

After you've reviewed the plan with your PM or EM, select the checkbox for your group. If you can't meet with the PM or EM for some reason (perhaps they're on PTO), append that information to the end of the line and leave the checkbox cleared.

Stage devopsmonitor

Stage devopspackage

Stage devopsverify

Stage devopsfoundations

Stage devopsai-powered

Stage devopscreate

Stage devopsplan

Stage devopsfulfillment

Stage devopsdata_access

Stage: Dedicated, group: Switchboard

Stage devopsgitlab delivery

Stage: Production engineering

  • Group being disbanded

Stage devopstenant scale

Stage devopsapplication security testing

Stage devopssecurity risk management

Stage devopssoftware supply chain security

Other events and team efforts this milestone

  • Managers check the Developer Advocacy Team Calendar for Hackathons and other events that may impact team velocity this milestone. List the events and dates, and let the team know in the tw-team Slack channel, and as a read-only in the TW Team meeting.

Group changes

display: table
title: Group changes
description: Group changes we are tracking this milestone
fields: title, milestone
limit: 20
query: project = "gitlab-org/technical-writing/team-tasks" AND label = "TW group change" AND state = opened

Events

  • None

✂️ UX Paper Cuts

Epic that links to UX Paper Cuts team planning issue for this milestone. Issues and MRs have regular stage/group labels.

TW recurring tasks

TW team KRs

Other team KRs

List of KRs from other teams with Technical Writing impact or involvement this quarter:

  • None

Stage lead issues

Stage TWs Issue
devopsapplication security testing @rdickenson @phillipwells #1309 (closed)
devopsverify @lyspin @marcel.amirault @rsarangadharan #1305 (closed)
devopsai-powered @jglassman1 @sselhorn #1306 (closed)
devopscreate @aqualls @brendan777 @jglassman1 #1307 (closed)
devopsplan @msedlakjakubowski #1308 (closed)

Docs site work

Edited by Suzanne Selhorn