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.5 Dev Note Tracking Issue #59155

Closed
32 tasks done
Leonardus-Nugraha opened this issue Feb 18, 2024 · 25 comments
Closed
32 tasks done

6.5 Dev Note Tracking Issue #59155

Leonardus-Nugraha opened this issue Feb 18, 2024 · 25 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

@Leonardus-Nugraha
Copy link

Leonardus-Nugraha commented Feb 18, 2024

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.

  • 🗓 Deadline March 4th, 2024

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

  • 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)

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 and has 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 it has dev note


To Do

viewScriptModule: dev note preview - Published

Site editor and page editor unification: dev note preview

Deprecate outer margins: dev note draft

Font Library: dev note draft

Misc Dev Notes: post draft

Block Hooks - Published

Block Bindings - Published

@Leonardus-Nugraha Leonardus-Nugraha added [Type] Developer Documentation Documentation for developers [Type] Tracking Issue Tactical breakdown of efforts across the codebase and/or tied to Overview issues. labels Feb 18, 2024
@t-hamano
Copy link
Contributor

t-hamano commented Feb 19, 2024

This is a dev note for #53467. Perhaps it would be good to include it as part of the miscellaneous dev note.

#53467 (comment)

@andrewserong
Copy link
Contributor

andrewserong commented Feb 19, 2024

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.

@t-hamano
Copy link
Contributor

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.

@sirreal
Copy link
Member

sirreal commented Feb 21, 2024

The dev note for #57303 was submitted in this comment: #57303 (comment)

@mikachan
Copy link
Member

Noting that the Font Library items listed above should be covered in a dev note that's being drafted here.

@ockham
Copy link
Contributor

ockham commented Feb 29, 2024

The Block Hooks in 6.5 Dev Note now has a draft available in make/core.

@cbravobernal
Copy link
Contributor

The Interactivity API in 6.5 Dev Note has a draft available in make/core.

@jsnajdr
Copy link
Member

jsnajdr commented Mar 1, 2024

@youknowriad
Copy link
Contributor

A draft of the "unification of post and site editors" dev note is available on make/core.

This addresses the three following PRs:

#57158
#57012
#56000

@youknowriad
Copy link
Contributor

#54494 doesn't seem worth a dev note to me.

@retrofox
Copy link
Contributor

retrofox commented Mar 3, 2024

@sirreal
Copy link
Member

sirreal commented Mar 4, 2024

I've added a link to the viewScriptModule dev note preview.

@sirreal this one has been reviewed

Thanks! Does that mean it's OK to publish now?

Edit: I've confirmed yes 🙂

@andrewhayward
Copy link
Contributor

andrewhayward commented Mar 4, 2024

@carolinan
Copy link
Contributor

Is there no plans for a dev note for the pattern overrides?

@Leonardus-Nugraha
Copy link
Author

@carolinan I didn't find PRs related to pattern overrides labelled 'needs dev note'. Could you help me point to that if any?

@mcsf
Copy link
Contributor

mcsf commented Mar 4, 2024

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.

@jorgefilipecosta
Copy link
Member

Dev note for footnote support in all CPTs available at #57353 (comment).

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.