This post summarized the editor chat from Wednesday, June 14, 2023, 14:00 UTC (agenda) held in the #core-editor channel moderated by @bph – Full transcript
Announcements
- Gutenberg 16.0 is now available for download from the plugins repository. Release lead The community member ultimately responsible for the Release., Nick Diego published the release post What’s new in Gutenberg 16.0? (14 June)
- WordPress 6.3 is less than two weeks away from Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 (June 27) This is the second to last Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ release, and it needs lots of testing.
- The FSE Call for testing 24 is a great way to learn about the new features and at the same time provide feedback before the beta releases, deadline for comments is June 28
New Developer Blog (versus network, site) posts
Project updates
Task Coordination
@Leonardus Nugraha, 6.3 release squad docs team,
published the Dev Notes tracking issue for WordPress 6.3. It’s the first time, Leo is working on this, so he definitely requires your help finding all the PRs that would need a dev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase..
@ndiego 6.3 Editor Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. release squad
If anyone is looking to contribute and work on an issue, the items on the Editor Tasks for 6.3 board are the most important for 6.3
Open Floor
@bernhard-reiter
This is more of an early pre-announcement, but @fullofcaffeine has been working on a PR that will enable us to publish a point release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. for a previous version series even if a new stable release has already been published. (E.g. if the current Gutenberg version is 15.9.1, and we discover a serious bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. in 15.8.1, the changeset will allow us to publish a 15.8.2 release with a bugfix.) Since it is a somewhat substantial change to the release GHA workflow, we’re planning to land it only after GB 16.1 has been published, in order not to interfere with WP 6.3. We’re currently targetting July 5 (see). Here’s some more info shared by @fullofcaffeine.
@Hanzala
“[I] missed last few meetings due to some work stuff but it feels good to finally join today’s meeting. Hope to contribute on some task in a coordinated way. just wanted to share that”.
Birgit: “It’s good to have you join us today and we are all looking forward to your contributions. Bangladesh and WPDeveloper have been contributing quite a lot lately Especially for 6.2. Thank you!
Hanzala: “Yeah many people are really interested. Hope we can find some impactful contributors.”
Props to @paaljoachim for review.
#core-editor, #core-editor-summary, #gutenberg, #meeting, #summary
