Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Product design responsibility #22284

Merged
merged 6 commits into from
Sep 25, 2024
Merged

New Product design responsibility #22284

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f1b758c
New Product design responsibility
noahtalerman Sep 20, 2024
736b417
Update handbook/product-design/README.md
noahtalerman Sep 23, 2024
dcfb7ec
Update handbook/product-design/README.md
noahtalerman Sep 23, 2024
c7d6041
Update handbook/product-design/README.md
noahtalerman Sep 23, 2024
2e8da95
Merge branch 'main' into noahtalerman-patch-11
noahtalerman Sep 23, 2024
0b8e2fa
Update handbook/product-design/README.md
lukeheath Sep 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions handbook/product-design/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,17 @@ available in Google Drive.
Some of the data is forwarded to [Datadog](https://us5.datadoghq.com/dashboard/7pb-63g-xty/usage-statistics?from_ts=1682952132131&to_ts=1685630532131&live=true) and is available to Fleeties.


### Prepare reference docs for release
noahtalerman marked this conversation as resolved.
Show resolved Hide resolved

Every change to how Fleet is used is reflected live on the website in reference documentation **at release day** (REST API, config surface, tables, and other already-existing docs under /docs/using-fleet).

To make sure this happens, first, the [DRI for what goes in a release](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris) @ mentions the [API design DRI](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris) in a message in [#help-engineering Slack channel](https://fleetdm.slack.com/archives/C019WG4GH0A) when we cut the release candidate (RC).

Next, the API design DRI reviews all user stories and bugs with the release milestone to check that all reference doc PRs are merged into the reference docs release branch. To see which stories were pushed to the next release, and thus which reference doc changes need to be removed from the branch, the API design DRI filters issues by the `~pushed` label and the next release's milestone.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@georgekarrv @sharon-fdm Note that with this change it's more important to add the ~pushed label to a user story if it was planned for a release and is not going to be included. We'll be using that to determine which doc changes need to merge, and which need to wait.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Roger.


To signal that the reference docs branch is ready for release, the API design DRI opens a PR to `main`, adds the DRI for what goes in a release as the reviewer, and adds the release milestone.
noahtalerman marked this conversation as resolved.
Show resolved Hide resolved


## Rituals
<rituals :rituals="rituals['handbook/product-design/product-design.rituals.yml']"></rituals>

Expand Down
Loading