Agenda for today’s 3.7 chat at time 20:00…

Agenda for today’s 3.7 chat at 20:00 UTC:

• It looks like we’ve closed more than 800 tickets since 3.7 started. We increasingly need to develop some patterns here so we can sustain this. Let’s talk about how we can start targeting individual components, keywords, ticketticket Created for both bug reports and feature development on the bug tracker. statuses; and also we need to start to getting the 3.7 report in shape.
• Discuss a timeline for the release. When should we have stuff ready for 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. 1, when should we hit 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)., and when should we aim to release? What should we done for beta 1, versus what must be done for RC1?
• The JavaScriptJavaScript JavaScript 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/. working group decided on QUnit as our JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. testing framework. There is an initial 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., which necessitates we move our PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher tests into a directory. Quick discussion and decision on where it goes.
• Approve a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. organization plan to use milestones for features-as-plugins and for Twenty Fourteen.
• Work is starting on upgrades. We need to build out a proper task list and see where people are willing to help. (More on that in this blog post.)
• Version 3.6.1 discussion and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. It’s been four weeks, we should get things ready.

I’d like to keep this chat to 30-40 minutes, followed by 20-30 minutes of unstructured office hours / Trac ticket review / 3.6.1 triage. The 3.8 meeting starts right after, at 2100 UTC.

#3-7, #agenda