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.

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

merged 6 commits into from
Sep 25, 2024

Conversation

noahtalerman
Copy link
Member

Prepare reference docs for release

Prepare reference docs for release
@noahtalerman
Copy link
Member Author

@lukeheath I chatted w/ @rachaelshaw about Rachael taking on this responsibility.

We're good to go 🚀

rachaelshaw
rachaelshaw previously approved these changes Sep 20, 2024
handbook/product-design/README.md Show resolved Hide resolved
handbook/product-design/README.md Show resolved Hide resolved
handbook/product-design/README.md Outdated Show resolved Hide resolved

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.

Copy link
Member

@lukeheath lukeheath left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@Sampfluger88 Sampfluger88 merged commit 345d35c into main Sep 25, 2024
4 checks passed
@Sampfluger88 Sampfluger88 deleted the noahtalerman-patch-11 branch September 25, 2024 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

6 participants