15 10 6 tickets between us and launch…

15 10 6 tickets between us and launch. Still need 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. 4 and an RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).. The tickets:

Needs Dev / Bug Wrangler Feedback

  • #19338 Welcome Panel and no JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. don’t mix well — Not sure how we missed putting in a no-js version, but we did. Need one. @dkoopersmith was owner of feature, @azaozz has done lots of the no-js stuff in wp, and @joncave made the ticketticket Created for both bug reports and feature development on the bug tracker. and wrote a 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.. Huddle and work it out. (@jane)
  • #17975 _default_wp_die_handler css referencing logic is fragile and doesn’t always work (@jane)

Has Patch / Needs Testing

  • #19020 Content Updates for Help Tabs — Tedious. Will finish before before string freeze at RC. Mostly same strings, just moved around a bit. @chexee, @jane and whoever wants to help with some copy paste drudgery patching.
  • #19191 Improve adminadmin (and super admin) menu tab navigation — Gotta be keyboard accessible! @dkoopersmith or @azaozz need to check out patch by John Kleinschmidt on ticket. (@jane)
  • #19127 Welcome Panel should be displayed for the first administrator — Panel itself is done, but needs code underneath. @nacin is on this today. (@jane)
  • #19326 jQuery 1.7.1 — They just released this update. There were some issues with 1.7. (@jane)
  • #19292 Not found errors due to sanitization in sanitize_title_with_dashes — Mark’s patch being reviewed.
  • #19125 CPT as a submenu item does not get the correct classes when adding new (@jane)
  • #18693 New feature pointers — These are in, but in some browsers aren’t positioning correctly (fixed, [19416]). Also need a little RTL love, see #19335. (@jane)

Patch Needs Refresh

  • #18880 Back compatback compat Backward compatibility - a desire to ensure that plugins and themes do not break under new releases - is a driving philosophy of WordPress. While it is a commonly accepted software development practice to break compatibility in major releases, WordPress strives to avoid this at all costs. Any backward incompatible change is carefully considered by the entire core development team and announced, with affected plugins often contacted. It should be noted that external libraries, such as jQuery, do have backward incompatible changes between major releases, which is often going to be a greater concern for developers. for the admin_user_info_links filterFilter 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. (@jane)

Needs Patch

  • #19088 AccessibilityAccessibility 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) for the admin bar — Screen readers, tabbing, etc. (@jane)
  • #18742 New post-update screen — screen itself is done (translators, might want to get a head start, lots of new strings), but needs code to tell when to show it/to whom. Maybe some RTL love also. @nacin doing the when-to-show code. (@jane)
  • #19320 wp_tiny_mce() cannot call wp_editor(), and other issues — @nacin and @azaozz duking it out on the ticket. (@jane)
  • #19335 Make feature pointers nice for our RTL users (@jane)
  • #18467 Standardize Language on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Update — @nacin working on it.

#3-3