-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
6.5 Dev Note Tracking Issue #59155
Comments
This is a dev note for #53467. Perhaps it would be good to include it as part of the miscellaneous dev note. |
I've added dev notes as comments to the following PRs:
These features don't require a separate dev note, so can also be added as part of the miscellaneous dev note. |
I added a new #45731 to the list and wrote a dev note. I think it's fine as part of the miscellaneous dev note. |
The dev note for #57303 was submitted in this comment: #57303 (comment) |
Reminder for PR owners to draft the dev notes by the end of this week if possible #58620 @andrewhayward |
Noting that the Font Library items listed above should be covered in a dev note that's being drafted here. |
The Block Hooks in 6.5 Dev Note now has a draft available in make/core. |
The Interactivity API in 6.5 Dev Note has a draft available in make/core. |
Dev note for #58262 ( |
#54494 doesn't seem worth a dev note to me. |
Dev note for #55337 ( |
@sirreal this one has been reviewed |
Edit: I've confirmed yes 🙂 |
Is there no plans for a dev note for the pattern overrides? |
@carolinan I didn't find PRs related to pattern overrides labelled 'needs dev note'. Could you help me point to that if any? |
There is an active discussion going on on aspects of the feature and its API which needs to be settled before the appropriate dev note can be finalised. |
Dev note for footnote support in all CPTs available at #57353 (comment). |
Tracking all Dev Notes from Gutenberg plugin releases 16.8 - 17.7
Please read the information below carefully. If you have questions, connect with @Leonardus-Nugraha via Slack or comment here.
Not all developer-related information needs to be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already make decisions on some features if it warrants a stand-alone blog post or if the information will be part of a group post.
Stand-alone post
To streamline the process and eliminate bottlenecks, all writers of stand-alone dev notes will write the dev notes on the Make Core Blog.
Instructions
Part of a group post
If the information related to your PR will be part of a group post, please write the dev note in a comment on the PR, so it can be reviewed and, if necessary commented on, by the release docs team or a reviewer.
Before you start writing 📣 please read the handbook pages:
The list is incomplete. We are in the process of reviewing plugin release changelogs and add them as we progress on the task.
There are two labels:
needs dev note
andhas dev note
If you worked on a feature/module/component that definitely needs a dev note, please assign the label
needs dev note
If you already added the Dev Note to the make blog on draft or as a comment on the PR, please label ithas dev note
To Do
Composite
implementation #58620 @andrewhaywardisPressed
inButton
component #54740 @andrewhaywardviewScriptModule
: dev note preview - PublishedSite editor and page editor unification: dev note preview
Deprecate outer margins: dev note draft
__next36pxDefaultSize
#58703 @mirkaFont Library: dev note draft
Misc Dev Notes: post draft
buttonBehavior
attribute #53467 @t-hamanoBlock Hooks - Published
Block Bindings - Published
The text was updated successfully, but these errors were encountered: