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

6.2 Dev Note Tracking Issue #47771

Closed
47 tasks done
bph opened this issue Feb 6, 2023 · 35 comments
Closed
47 tasks done

6.2 Dev Note Tracking Issue #47771

bph opened this issue Feb 6, 2023 · 35 comments
Labels
[Type] Developer Documentation Documentation for developers [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@bph
Copy link
Contributor

bph commented Feb 6, 2023

Tracking all Dev Notes from Gutenberg plugin releases 14.2 - 15.1

Please read the information below carefully. If you have questions, connect with @bph or @zzap via Slack or comment here.

  • 🗓 Deadline March 3rd, 2022

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 decision 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 receive privileges on the Make Core Blog. (Please connect with @bph or @zzap, if you need access)
Instructions

- Create your note in a new post, - Save as Draft - Enable public preview - Share the link to the public preview in a comment below, as "ready for review" - "For dev notes, each one must have at least two reviewers" ([Handbook](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/))
## 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:

- ⭐️ [Writing developer notes](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/) - ⭐️ [Style & Substance section](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#style-and-substance) of the Post & Comment Guidelines for Make Blog - ⭐️ [Documentation Style Guide](https://make.wordpress.org/docs/style-guide/) - Good for reference, when in doubt, especially when English is not your native language.

The list is incomplete. We are in the process of reviewing plugin release changelogs and add as we progress on the task.

There are two labels:
needs dev note and has dev note

If you worked on a feature/module/component that definitely needs dev note, please assign the label needs dev note If you already added the Dev Note to the make blog on draft or as comment on the PR, please label it has dev note


~- #46212 @ellatrix ~ not in core for 6.2

Navigation

CustomCSS

InspectorControls + Split Block Tools

Experimental APIs

WP_HTML_Tag_Processor

Blocks

Theme.json /Appearance Tools

Components @ciampo @mirka

Global Styles

Layout/ Templates

Deprecations/Removals

Create Block scaffolding

Pattern and Pattern Directory

ServerSideRender package

@bph bph added [Status] In Progress Tracking issues with work in progress [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. [Type] Developer Documentation Documentation for developers labels Feb 6, 2023
@ciampo
Copy link
Contributor

ciampo commented Feb 6, 2023

Just flagging that @noisysocks is on parental leave as of today, I guess that the dev note for #45960 could be written by @ramonjd or @andrewserong who also helped on that PR?

@bph
Copy link
Contributor Author

bph commented Feb 6, 2023

Appreciate the flag @ciampo - I updated the ping for the PR #45960 :-)

@gziolo
Copy link
Member

gziolo commented Feb 6, 2023

#44185 @gziolo

That were code changes that propagated what was included in the dev note for WordPress 6.1.

@t-hamano
Copy link
Contributor

t-hamano commented Feb 6, 2023

@ntsekouras
Copy link
Contributor

For some blocks with caption, a toolbar button has been added to add / remove caption. Should a Dev note be written about these UI changes as well?

I don't think a dev note is needed for these, as they are UI changes.

@bph
Copy link
Contributor Author

bph commented Feb 6, 2023

Totally agree, @t-hamano + @ntsekouras - Keep the questions coming, though.

@oandregal
Copy link
Member

@bph I've added @pbking and @mikachan for #43337 as they were the ones who implemented that feature :)


In the case of #45171 there's only 1 thing worth having a devnote about (I presume the performance improvements do not require a devnote?). Here's the suggested text:

wp_theme_has_theme_json

WordPress 6.2 introduces a new method called wp_theme_has_theme_json(), that returns whether the active theme or its parent has a theme.json file. The goal is to provide 3rd parties with a public API they can use to query the active theme for this information.

Being so small a note, I presume it can be published as part of a bigger one?

@bph
Copy link
Contributor Author

bph commented Feb 7, 2023

@oandregal thanks for the flag, if you want to combine PRs dev notes that is a great way to serve all the details in one post. This might go well with #45089 and others round theme.json and providing extenders with ways to interact with the settings.

@oandregal
Copy link
Member

if you want to combine PRs dev notes that is a great way to serve all the details in one post.

I don't plan to, as that's my only and single contribution, and it's quite small :) I'll let others chime in. If there's no better place, it could go as part of the "miscellaneous changes" note (example in 5.9)?

@t-hamano
Copy link
Contributor

t-hamano commented Feb 9, 2023

I added a "ServerSideRender Package" section and wrote a dev note to #44491.

@draganescu
Copy link
Contributor

I am not sure that #44739 needs a dev note, it was more like an oversight ... @Mamaduka what do you think?

@Mamaduka
Copy link
Member

Mamaduka commented Feb 9, 2023

@draganescu probably not. It's a new feature for users.

@getdave
Copy link
Contributor

getdave commented Feb 9, 2023

#46885 @getdave

This was a selector originally added in #46531 and then subsequently modified in #46885. We then decided due to its instability to make it private which I did in #47638.

As a result we don't need a dev note as it's a private API.

@getdave
Copy link
Contributor

getdave commented Feb 9, 2023

Fully remove Navigation Editor screen and associated edit-navigation package #47055 @getdave

Please see dev note here.

@andrewserong
Copy link
Contributor

andrewserong commented Feb 10, 2023

I guess that the dev note for #45960 could be written by @ramonjd or @andrewserong who also helped on that PR?

Thanks for the ping @ciampo! I've added a draft dev note to the PR for the Style Book here: #45960 (comment)

Update: draft dev note blog post is here: https://make.wordpress.org/core/?p=102735&preview=1&_ppp=03ed6e05f5

@andrewserong
Copy link
Contributor

Since Ramon isn't around, I've added a draft dev note to cover these two over in this comment: #42489 (comment)

@aaronrobertshaw
Copy link
Contributor

InspectorControls + Split Block Tools

I added a draft dev note in #47045 (comment) that aims to cover all the closely related PRs under the "InspectorControls + Split Block Tools" section in this issue's description.

@adamziel
Copy link
Contributor

I marked #43386 as done – it doesn't require a dev note as it's a special case of an API specifically designed not to be used by contributors. I may write a separate post about it, but not a dev note.

@andrewserong
Copy link
Contributor

andrewserong commented Feb 14, 2023

I've drafted a dev note in this comment (#45300 (comment)) to cover these PRs under the umbrella of introducing the minHeight dimensions block support

I've drafted a dev note for the sticky position block support in this comment: (#46142 (comment)) — I've added a couple of "why" headings there to provide answers to some of the feedback raised so far.

@tellthemachines
Copy link
Contributor

Dev note for children of flex layout blocks here!

@andrewserong
Copy link
Contributor

Added a small draft dev note to be included in a Misc dev note in this comment: #46388 (comment)

@carolinan
Copy link
Contributor

I have removed [ ] #43337 @pbking @mikachan from the list because the feature is not in 6.2.

@carolinan
Copy link
Contributor

Short dev note for per-block custom CSS #46571 (comment)

@ciampo
Copy link
Contributor

ciampo commented Feb 22, 2023

I made a few changes to the list of components-related PRs:

I then went ahead and added dev notes for all of the PRs in the updated list.

@adamziel
Copy link
Contributor

adamziel commented Feb 24, 2023

I've drafted a dev note for #42122 and #46138 in a comment at [Heading block] Add a wp-block-heading CSS class

I also drafted a dev note for #45089 in a comment there.

@bph
Copy link
Contributor Author

bph commented Feb 28, 2023

Thank you so much @adamziel I added the Heading block dev note to the Misc Editor post
And @ndiego drafted the dev note for #45089 on the make blog. (Thank you, Nick)

@youknowriad
Copy link
Contributor

@bph I've drafted a dev note for the removed APIs here #46106 (comment) We might want to include this in a "miscellaneous editor changes" dev note.

@bph
Copy link
Contributor Author

bph commented Feb 28, 2023

@ciampo Thank you so much for re-organizing the Component section of the DevNote tracking issue and writing the small snippets Dev note for each listed PR.
I put them all into a stand alone post in the Make Core Blog with your name on it. Would you please review it, just to double-check, I didn't have the copy/paste devil on my shoulder.
Please edit as you see fit.

The two deprecation items, useAnchorRef and DateTimePicker, I added the deprecation section of the Misc Editor post

@bph
Copy link
Contributor Author

bph commented Mar 7, 2023

Dev Notes published for WordPress 6.2

Miscellaneous Editor changes in WordPress 6.2

Huge Thank you to all who contributed to dev notes and helped to review them

If you find anything missing, please let me know so we can correct that oversight quickly, preferable before the release of 6.2 final release.

@draganescu

This comment was marked as resolved.

@bph

This comment was marked as resolved.

@draganescu

This comment was marked as resolved.

@bph

This comment was marked as resolved.

@bph

This comment was marked as resolved.

@bph bph closed this as completed Mar 8, 2023
@bph
Copy link
Contributor Author

bph commented Mar 10, 2023

The Field Guide for WordPress 6.2 was published March 9th at 5am UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Developer Documentation Documentation for developers [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
Status: Done
Development

No branches or pull requests