These are my rough highlights from yesterday’s kick-off meeting. They emphasize who is working on what.
Preliminary session management interface: https://i.imgur.com/sHz2oeV.png
There’s a repo: https://github.com/johnbillion/wp-session-manager/
Various tasteful and sensible people:
“We might end up calling this the Keep Ryan Happy release”
“the rboren happy release, for those who don’t know, is fixing and improving mobile stuff”
“ryan deserves happiness. Not just because I want mobile and media too :)”
Also on the list is improvements to the UI User interface when installing and updating plugins, themes, and core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. I want to get rid of the ancient UI which has been in core since we first started doing updates inside core
So, one of the things I originally wanted to do (and avryl had in early versions of the Focus 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) was to do some fading of the rest of the UI when you are actively typing into a post. I think this would get us the rest of the way to DFW’s feature set.
So my goal for 4.1 would be to remove DFW completely.
We also could/should do the fancy scroll behavior for the menu like we do for post side metaboxes.
1) the theme will be ready by October 25
2) if the theme is not on track for that, the default themes are matt’s pet project, and he will allocate appropriate design and development resources to make sure it will be ready by October 25
One last feature that I forgot, I’d love to get the language chooser on the General Settings screen to be able to download and install new languages like we planned for 4.0 but had to get punted
mentioned this a couple weeks ago i believe, ericandrewlewis and i are experimenting with tackling some tickets as a plugin to start so we can move faster: https://github.com/helenhousandi/wp-19867-9864
currently working on a branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". that uses select2 to help with scaling issues with the users dropdown – would look to bring this to pages, tags/nonhierachical taxonomies, and the multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site add user and add site forms.
I’d like to do some work with markoheijnen on getting a few of the image manip 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. improvements in before image-flow
netweb and helen:
#22435 Export API <- Would be great to get this in, has-patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., needs-testing, adds export unit tests to core and that will help other export related tickets.
I’ll be working on syntax and internal improvements for WP_Tax_Query, WP_Date_Query, WP_Meta_Query. Berzerk test coverage, support for multi-relational/nested queries, some other goodies. See eg #29738
I want to get a bunch done around multisite unit testing and rewriting some old junk to clean things up a bit. This should help us start moving steadier with other improvements.
Also want to investigate moving WP_Meta_Query to subqueries rather than JOINs because of the massive crappiness of JOINing the meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tables. May not have time for 4.1, but will start doing some benchmarks. #24093
https://core.trac.wordpress.org/ticket/24093 Future Release, sc0ttkclark->(no owner), new, WP_Meta_Query is inefficient when referencing the same keys in “OR” query
I’ll be evangelizing flow and visual records. http://simp.ly/publish/rBkqyq