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

What's new for developers? (June 2024) #264

Open
justintadlock opened this issue May 13, 2024 · 9 comments
Open

What's new for developers? (June 2024) #264

justintadlock opened this issue May 13, 2024 · 9 comments
Assignees

Comments

@justintadlock
Copy link

This is a rolling discussion for a new monthly series that is intended to keep track of the items, PRs, Trac tickets, and Make blog posts that are interesting/important for developers. The goal is to publish a post on the 10th of each month with the previous month's updates.

Everyone is welcome to contribute to this monthly document. If you find something interesting, just create a new reply to this discussion below.

Google Doc: https://docs.google.com/document/d/1I3msotKyqE1ChKJz5Ha45u2Gl9eytL8U671h4uJxArI/edit?usp=sharing

Resources to track:

Writer: @ryanwelcher will be the primary author on this post.

Copy link

Heads-up @bph @adamziel @bgrgicak @pbking @mikachan: To include your project's news for developers, please add the information or a link as a comment to this issue. Deadline 8th of next month

@justintadlock
Copy link
Author

Some tickets to watch that may include breaking CSS changes for themes (particularly around CSS resets):

@juanmaguitar
Copy link
Contributor

@justintadlock @bph Has it been discussed previously sharing the resources used to curate this content ("Resources to track") in the post itself? I think it could be interesting for developers as a way to help discover how to keep track of changes happening in WordPress.

@justintadlock
Copy link
Author

I don't see anything necessarily wrong with some sort of resources section, but I would say that I use that list as more as a rough guideline. The only resources that I use 100% of the time are:

  • Gutenberg changelog from the repo
  • Trac changesets (you have to manually configure this each month)
  • Replies to the monthly ticket

I also note things from other sources like Twitter, Facebook, and third-party blogs (none of which we can link to).

@annezazu
Copy link

annezazu commented Jun 6, 2024

Want to flag this PR WordPress/gutenberg#61577 I'm not sure if it'll be ready for June but I think it's the perfect thing to include whenever it lands as it'll need feedback and testing from plugin authors.

@ryanwelcher
Copy link

Want to flag this PR WordPress/gutenberg#61577 I'm not sure if it'll be ready for June but I think it's the perfect thing to include whenever it lands as it'll need feedback and testing from plugin authors.

The PR is still in draft but it it gets merge before Monday, we can probably get it added.

@ryanwelcher
Copy link

This is ready for review

@justintadlock
Copy link
Author

Moved this to 2nd review since the first was completed.

@justintadlock
Copy link
Author

Nice work, @ryanwelcher! Second review is done and ready. Once finished, you're ready to publish on the 10th!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done w/ 2nd review
Development

No branches or pull requests

5 participants