-
Notifications
You must be signed in to change notification settings - Fork 427
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
Conversation
Prepare reference docs for release
@lukeheath I chatted w/ @rachaelshaw about Rachael taking on this responsibility. We're good to go 🚀 |
Co-authored-by: Sam Pfluger <[email protected]>
Co-authored-by: Sam Pfluger <[email protected]>
Co-authored-by: Sam Pfluger <[email protected]>
Co-authored-by: Noah Talerman <[email protected]>
|
||
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Roger.
There was a problem hiding this 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!
Prepare reference docs for release