Dev Chat Agenda for March 15th (4.7.4 week 2)

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

This is the agenda for the weekly dev meeting on March 15, 2017 at 15:00 CST:

4.7.4 planning
Browser support (note discussion just prior at March 15, 2017 at 12:00 EDT)
Confirmation on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team reps
Customize team update (media widgets & call for testing)
REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. team (call for help on JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. Leadership for WP Adminadmin (and super admin) implementations)
General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-7-4, #agenda, #core, #dev-chat

Paul Bearne 5:51 pm on March 14, 2017

Can we talk about adding @covers and @uses to all the phpUnit tests?

This will allow us to create covers reports and message how we are doing.

I would like to propose that we require for all new / updated tests and that the code committers commit updates with these added ASP.

FYI
the notation is
for a the function that is been tested
@covers classname::function_name // if in a class
@covers ::function_name // if global

for any function the test that is not been test we need to add a @uses
@uses function_name

Myself and another dev are planning to bliz this if we can get agreement to tackle it, but happy to see others wade in.

Paul
- Pascal Birchler 6:10 pm on March 14, 2017
  
  Sure, we can do that during open floor / general announcements. Personally, I’m not against doing this for new/updated tests. But I also couldn’t get the coverage reports working, which makes it kinda useless.
  
  Related: #39237, #39265.

Comments are closed.

Welcome!

Communication

Share this: