We’re getting 3.3 ready for beta Here’s the…

We’re getting 3.3 ready for 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.. Here’s the gist of how things stand:

  • We’re doing daily (almost) 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. scrubs in #wordpress-dev to drive down the ticket count.
  • Nacin is finishing up WP_Screen and the media button merge.
  • Koopersmith is finishing up tabbed help and flyout menu styling.
  • Pointers need some styling fixes to be called done enough for 3.3. Pointers will probably be for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. only use in 3.3.
  • Adminadmin (and super admin) bar needs final walk through and tweaks.
  • Welcome box and about this version page need final feedback and tweaks.
  • Some of the responsive admin work will be pushed to 3.4 so we have more time to get large screens looking the way we want. Ozz and Jaquith are on it.
  • Jane will check all UIUI User interface/UXUX User experience feedback tickets and leave comments.
  • All task (blessed) tickets should be updated with a comment on current status by the end of the day.
  • I will stroke my beard in a diabolical manner while everyone else works.
  • Okay, besides that I will be scrubbing bugs, working on more unit tests, and getting coffee for the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. guys.

#3-3, #status