It’s time for another Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Group update.
This one coming late, due to WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe.
On the 3.7 Release:
- 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 shipped on schedule
- Beta 2 shipped last night
- Core upgrade reverts for partial upgrade failures now in core for Automatic Updates ().
- If the stars align, we hope to see RC1 within a week from now. To accomplish this, @nacin has requested assistance with a few remaining important tickets. You can also check Report 6 for a quick rundown.
On the 3.8 Release:
- @samuelsidler posted, clarifying that feature plugins that want to be considered for 3.8 should be ready by October 14th. This means ready that the beginning of the merge window, rather than at the end. This is coming up quickly.
- @nacin posted a potential roadmap for multisite which is suggested reading if you’re at all interested in multisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. or domain mapping.
Important Notes from this week:
- Landed clearing of transients on DB Upgrade 
- Landed first run of Automatic Upgrades; disabled by default (can enable with filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.) 
- Remaining enhancements still at 111, which is 111 more than we really want to be able to release. Called all hands on deck to help prune.
3.8 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 Group Highlights:
Chatted with @sams about updates from the various plugin teams.
The current plan is to pass on (with his assistance) highlights when they happen, or are most likely to affect the other groups, since otherwise there’s much more status than any of us care to keep in mind at once.
- MP6: Working on color schemes. Quite close to something that fits core Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and ready for polishing prior to the merge window.
- Omnisearch: Up for user testing. Next chat tomorrow.
 Forgot to mention (and remembered immediately after hitting post, of course), that @DrewAPicture now has guest commit for 3.7, so that he can beat inline docs into submission. Huzzah, good fellow! He is, per usual, the person to bug if you’d like to get involved, or have questions about the process. The activity on inline docs for hooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. can be tracked in . [/edit]
Apparently core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has seen to elect me, so I’ll be happy to hang with you all for the next few months.
Today, WordPress 3.6.1 was released mostly on schedule, closing up a few nagging security issues and bugs, which you can read about on the codex.
In part due to the release, our chat this week was a touch short. So, instead of a synopsis, I’ll quote the @nacin:
We need to bring down the ticket counts. Highest priority: 50% of all tickets need to be fixed or punted in the next week.
3.6.1 is out.
<3 you all.
So in terms of 3.7, that is indeed the goal for the next week.
I’m a bit behind on what the status of all the separate 3.8 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 groups is, so my mission for this week is to go through and catch up with each of them, so that I can report relevant details.
Last week’s meeting focused almost entirely on developing a global accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) statement for WordPress. It was decided that the statement should be broad in nature, and that it will generally support accessibility with links to more specific information maintained by the WordPress accessibility team.
The voluntary accessibility theme check process was mentioned, that process is nearly ready to launch. Theme developers who have accessible themes and want to go through the process will be given a tag of #accessible-ready if the theme passes the accessibility checks.
Much thanks to Mel Pedley @esmi for her guidance and leadership as team representative for the past 18 months. I will now serve as team representative.
You can also contact us with words of encouragement or feedback on Twitter @WPAccessibility.
Feature development is now in full swing. Over the last few weeks, a number of major decisions have been reached, and a lot of code has begun to land in trunk (or will be landing soon). About 50 commits in the last week.
- Twenty Thirteen landed on Monday, February 18. Already, 33 tickets have been filed. (Here’s a link to open Bundled Theme tickets for 3.6.) The team is holding twice-weekly meetings in IRC to triage and hammer out issues.
- Revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. has honed in on a promising UI featuring a slider. There’s already a functioning patch undergoing rapid iteration; that should hit trunk as early as next week. Also being worked on, lots of other smaller enhancements and bug fixes.
- Autosave (local storage, etc.) is aiming for a new patch later this week. This feature is more or less defined as a way to protect your content better than server-only autosaves have, and most of the how-should-it-work issues that blocked it have been resolved. This ties into revisions, so these two teams will be working very closely together soon.
- Post formats have the beginnings of a UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. in trunk. The current conversations have focused on theme and content compatibility. As in: what should the new theme template APIs look like? How should a theme declare support for these new “structured” post formats? How can we handle metadata-driven posts in older themes? How can we handle older posts without metadata in newer themes? Lots more going on here, stay tuned. #19570 #23347.
- Menus implemented some changes to the user experience for when the theme registers at least one menu location and the user has yet to create a menu. Very rough so far. More changes are being considered. #23119.
- Slashing changes hit core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. If you’re running trunk, it is quite the bumpy ride. We have been evaluating the original approach, and plan to make some major changes to it come next week in order to alleviate the many problems. #21767.
- Icons and admin UI… Icons hit core a few weeks ago; an initial pass at removing gradients to “flatten” the admin has also landed. More conversations and adjustments to follow. #23415 #23333.
- Editorial flow was dropped. This consisted of a small (but cool) feature, essentially allowing a user to submit a pending change to an already published posts. Unfortunately, the heavy overlap with both revisions and autosave, along with a number of other architectural concerns, made it impractical for now. (This team was also working on some API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. development, basically beefing up custom post status support, which didn’t end up having to do with the feature, and is still being considered.)
Feature freeze and 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 are scheduled for Wednesday, March 13, about three weeks away.
Hello everyone! Sorry for the delay in hearing from core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. here. We’re gonna participate in this whole new-fangled updates thing on schedule for now on. Your core team representatives are me and Cristi Burcă (@scribu). I expect future updates for core on make/updates to be a bit more focused on “this week” and “next week”, per the established pattern. For now, here’s a broad overview.
General timeline of events from the past month or so:
- WordPress 3.5 development came to a close on December 11.
- Mark Jaquith announced he was leading WordPress 3.6 on December 19. Aaron Campbell was chosen as his backup.
- Development of WordPress 3.6 started on January 2.
- WordPress 3.5.1 was originally targeted for as early as January 2. It slipped about two weeks because of the complexities of some of the bug fixes, then slipped further while the security team worked on some issues. Final release date was January 24.
Additionally, Helen Hou-Sandi and Sergey Biryukov were granted guest commit access for the 3.6 cycle. Helen has a focus on UI, Sergey on bugs. Jon Cave was also granted permanent commit access, after serving as a guest committer for three cycles over the course of a year. (Those two milestones have been and will continue to be the rule of thumb the lead developers follow.)
WordPress 3.6 development has been broken into 5 main feature teams:
- Revisions, led by Peter Westwood with Erick Hitter
- Autosave, led by Andrew Ozz with Mike Schroeder
- Post Formats, led by Helen Hou-Sandi with Pete Mall
- Editorial Flow, led by Daniel Bachhuber with Konstantin Kovshenin
- Nav Menus, led by Dave Martin with Drew Jaynes
Also, Sergey Biryukov is running maintenance and bug gardening, and working with me, Ryan Boren, and others on architecture. Lance Willett is running a Twenty Thirteen team that is expected to start working publicly come February.
Each team currently has twice-weekly office hours in #wordpress-dev to discuss and plan out their features. Personally, I like the feel of this and it reminds me of the rapid-fire discussions and decisions that needed to happen during 3.0’s development, with a new theme, post types, and of course the multisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. MU merge.
Because each team is mostly still scoping out features and making decisions, actual development has been fairly light so far. Mark has recognized that things are a bit behind based on the 3.6 schedule. Yesterday’s meeting went through a number of major issues with regards to post formats and nav menus, which was very helpful to set direction for both projects. And so, over the next week, feature development is expected to ramp up significantly.