The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
She congratulated everyone, NOT just the folks active in the chat, on an amazing job. Several CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers were especially pleased that 5.3 came in on schedule (🎉) with the biggest group of contributors ever.
Here are a few statistics:
12 weeks of development
A release squad with nine focus leads, covering every relevant component that got an update
645 contributors
658 bugfixes
A new default theme, Twenty Twenty
Lots of fun and new friends made
And much, much more!
Before release the squad counted at least 153 user-experience enhancements.
Highlighted Posts
The annual WordPress survey is open! Your feedback is not just appreciated – it’s vital to the future of WordPress. So please fill it out and share it everywhere you can think of.
Tanking the floor for a moment, @chanthaboune told the group this survey is new – not the same as last year – and is broader. Whether you’re a contributor, designers, developers, users or hosts, please participate!
Big thanks to everyone who has helped with testing so far! If that includes you, please keep testing and report any issues, concerns or enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas in a comment on Trac.
That’s how WordPress gets better and you get to shepherd your best ideas through the process.
@francina wrapped the discussion with a note that in the next few weeks the release leads will open a call for retrospective. Want to share some honest, constructive feedback? That’ll be your chance!
@marybaum said “I love that we have a #core-css channel. Does that mean Core CSSCSSCascading Style Sheets. is a component?”
@peterwilsoncc replied, “it’s closer to a focus than a component. Tickets can still be assigned to the affected component, eg Adminadmin(and super admin), Themes, etc. “
@sergey asked “If we have a `javascriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.` focus, should we add one for CSS as well?
After a few more comments from folks, @francina reminded all 30,000-plus potential attendees that we don’t make final decisions in devchat.
She asked the folks talking about CSS to follow this process:
Make a proposal on the Core blogblog(versus network, site)
Discuss
Come to a conclusion
Act
Here are the reports from other component maintainers:
@williampatton: “Themes component is looking good. Prepping for next release.”
@peterwilsoncc: “From the security team, now we have a Travis CI account that allows for private repos, we have the security tests running regularly. It should make it easier to find out if they’re passing during the release process.” and went on to ask @sergey if it was possible to add it to TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..
@mensmaximus asked whether “we ever change the user management screen to a tabbed interface. What is the current state and what do core devs think?”
@williampattonstarted with a general reply: “There are lots of thoughts on redesign for user management, but lots of ideas mean lots of decisions [making it] hard to reach agreement.”
A lively discussion followed. Hopefully the WordPress world will see some new ideas for an even more usable Admin experience!
(Ed. note: The UXUXUser experience discussion and the conversation below, about jQuery, happened at the same time, and you’ll see the comments jump from one to the other. Still, imo, both are worth your time and effort to decipher!)
@enrico.sorcinelli has “noticed that Juery’s `$` is no longer globally defined in admin.” That’s made some of their client sites cause issues with users’ code.
@clorith answered, “The jQuery `$` being globally available was a bugbugA 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..” That bug got fixed in one of the JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. updates in 5.3.
“Although it’s not ideal, reports of issues are fewer than expected, and the code errors would be within the pluginPluginA 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 code,” @clorith continued, adding, “I tend to lean towards leaving it being the right thing.”
