WordPress 4.6 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. 4 and current progress
Beta 4, the last beta before RC1, was released today. Please test and report all bugs you encounter on Trac.
There are still 9 open tickets that should be closed by RC1 next week. https://core.trac.wordpress.org/report/5
Dev notes 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., field guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page., email to plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party authors, 4.6 OMGWTFBBQ Draft Post
- @jorbin started outlining/drafting the field guide and will have a first draft in the next 24 hours for committers to review.
- The email to plugin authors will be sent in conjunction with the release of RC1.
- The 4.6 OMGWTFBBQ Draft Post is a post by the support team. You can find it here: https://make.wordpress.org/support/2016/07/4-6-omgwtfbbq-draft-post/. The support team especially appreciate suggestions for the “Not a Bug” section (these are items which are intentional changes, but may seem like a 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. or glitch to users offhand, like Dashboard fonts being different).
About page
Feature Pointers
There are no feature pointers planned for 4.6. If your feature is planning on using a feature pointers, please consider if you really need to.
Let’s find a tagline.
The brainstorming document can be found here. There are a few suggestions for a tagline already, but please add them to the doc. Please keep it serious.
Project updates
register_meta()
@jeremyfelt published an updated 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. for the recent change (https://make.wordpress.org/core/2016/07/20/additional-register_meta-changes-in-4-6/). It was shipped with beta 4 and also announced in the release post.
Font Natively
There are currently some alignment issues related to line-height. These will continue to be worked on as needed. Please report any other issues you may run into.
Component announcements/updates
None.
Open discussion
None.
You can read the full chat logs here: https://wordpress.slack.com/archives/core/p1469044867000364
#4-6, #dev-chat, #summary
