Dev Chat Summary – May 4, 2011

We have passed feature freeze, and are now in UIUI User interface week, leading up to a betaBeta 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. date of May 11. This week’s dev chat checked in on all the things we originally targeted for 3.2.

  • Drop PHP4 compat: This is done, but there are 1 or 2 places we went a little too far and need to revert to not break things.
  • Distraction-free Writing (dfw): Backend is ready. Need to change the buttons used for HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. actions, provide support for escape key, support theme styles, and fine-tune transition times. @azaozz owns this one.
  • List tables APIAPI 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: Not happening for 3.2. Westi’s basic summary of findings: More actions/filters/standardization and don’t support subclassing as an override method. Will try to get to this in 3.3.
  • Twenty Eleven (new default theme): Mostly finished, needs editor style support added.
  • IE6 EOL: Most agreed with @aarondcampbell‘s suggestion for the nag — IE < 8 could say "you're insecure" and anything < most recent could say "your browser is outdated" @aarondcampbell will write patchpatch 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., with confer with nacin about recent api work.
  • Speed improvements: There are lots and lots of speed improvements under the hood. Ryan has done time testing to prove it. If we have releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. video, Mark J suggested doing side by side view to show the difference. Nacin looked into PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 lazy loading, said it would not bring much improvement, so skipping it.
  • Partial coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. upgrades: work begun by @dd32, being finished by @nacin. Says nothing needs to be done in core, just on .org side re generating appropriate zips.
  • Style update: @dkoopersmith got first patch into trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. yesterday, had a large chunk of the update in it. Getting the rest in now, and then we’ll do a sweep to see what needs fixing/adding. Asking people to hold off on design feedback/requests/details until we’re ready, to avoid lots of tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. messages about details that are already being added, just haven’t been committed yet. Should be there in a day.
  • Trac tickets: feature requests and enhancements mostly getting punted since past feature freeze. If there’s a bugbug 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. you really wanted fixed, then get in there and find more people to test the patches on the ticketticket Created for both bug reports and feature development on the bug tracker.. Tickets withut patches will be punted.
  • Remainder of UI week will be dedicated to finishing the style update, and hitting small UI tickets that weren’t urgent/important enough to take attention away from core functionality, but that just makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). things a little bit nicer (it’s embarrassing that there are still things we put in during 2.7 that we said we’d clean up in 2.8 and then never got around to).

#3-2, #dev-chat, #meeting-notes