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

Outreach to component maintainers for Field Guide "But Wait, There is More!" section (WordPress 6.0) #40609

Closed
61 tasks done
bph opened this issue Apr 26, 2022 · 2 comments
Closed
61 tasks done
Assignees
Labels
[Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@bph
Copy link
Contributor

bph commented Apr 26, 2022

Publishing Field Guide
"Each Component team is sent a group direct message in Slack, pulling the list of maintainers from the individual component pages"

Example message:
It’s that time again Component Name component maintainer(s)… are there any tickets in the 6.0 release that you’d like called out in the Field Guide that aren’t already included in a Dev Note? As a reference, here are the ## tickets currently in the milestone for you: https://core.trac.wordpress.org/query?component=`ComponentName`&milestone=6.0&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority. Note that we intend to publish the Field Guide next week, so the sooner you can respond the better… thanks!

List of components

The link goes to the list of tickets for the milestone for the component. The number of tickets is in parentheses.
A blue check mark means maintainers were contacted or no issues.

@bph bph added the [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. label Apr 26, 2022
@bph bph self-assigned this Apr 26, 2022
@bph
Copy link
Contributor Author

bph commented Apr 26, 2022

@bph
Copy link
Contributor Author

bph commented May 10, 2022

Closing it now as the Field Guide was published and updated last week.

@bph bph closed this as completed May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
None yet
Development

No branches or pull requests

1 participant