Skip to content

Conversation

talldan
Copy link
Contributor

@talldan talldan commented Jul 18, 2025

What?

See - https://wordpress.slack.com/archives/C02QB2JS7/p1751597024760749

Makes a few changes to the gutenberg release docs and issue:

  • Clarifies how to request visual assets - the idea being to reduce the need to involve a designer:
    • Use the existing image in the media library for the featured image
    • Use the 'Gutenberg What's New' synced pattern for the main banner
    • Only request assets from design for high profile features (e.g. not sure if we need to clarify what a high profile feature is)
  • Adds a section about requesting a volunteer for the next release at the end of the process - the idea being to make the release process more self-managing rather than needing someone to have oversight of find volunteers.

@talldan talldan self-assigned this Jul 18, 2025
@talldan talldan added the [Type] Project Management Meta-issues related to project management of Gutenberg label Jul 18, 2025
Copy link

github-actions bot commented Jul 18, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: priethor <priethor@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@talldan
Copy link
Contributor Author

talldan commented Jul 18, 2025

Something I wasn't able to do is update the google doc here - https://docs.google.com/document/d/1D-MTOCmL9eMlP9TDTXqlzuKVOg_ghCPm9_whHFViqMk/edit?tab=t.0

I don't have access. I left suggestions though.

@talldan talldan requested a review from karmatosed July 18, 2025 08:30
Copy link
Member

@Mamaduka Mamaduka left a comment

Choose a reason for hiding this comment

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

Makes sense. Thank you, @talldan!

Copy link
Contributor

@priethor priethor left a comment

Choose a reason for hiding this comment

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

Thanks, Dan. I've applied your suggestions to the doc and gave you access in case you want to add anything else.

@Mamaduka Mamaduka merged commit c2842ff into trunk Jul 18, 2025
74 checks passed
@Mamaduka Mamaduka deleted the update/gutenberg-release-docs branch July 18, 2025 10:47
@github-actions github-actions bot added this to the Gutenberg 21.3 milestone Jul 18, 2025
USERSATOSHI pushed a commit to USERSATOSHI/gutenberg that referenced this pull request Jul 23, 2025
* Update release docs around visual assets process
* Add call for volunteer for next release to the process

Co-authored-by: talldan <talldanwp@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>
Co-authored-by: priethor <priethor@git.wordpress.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Project Management Meta-issues related to project management of Gutenberg
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants