Dev Chat Summary: November 22nd (4.9.1 week 1)

This post summarizes the dev chat meeting from November 22nd (agenda, Slack archive).

4.9 feedback + 4.9.1 planning

  • WordPress 4.9 was released last week, and so far 3 pressing issues have arisen that needs to be addressed in a timely manner:
    • #42573 (template file caching), #42574 (MEJS breaking things for some languages), and #42609 (file editing broken on Windows).
    • As we have a short timeline for this release, focusing on these 3 major issues for now, and planning a future point release for any other regressions appear to be the ideal way forward.
    • @johnbillion has volunteered to run the 4.9.1 release, backed by @sergeybiryukov, we're aiming to have 4.9.1-RC1 on Monday November 27th, with a tentative release date set for Tuesday November 28th.

Request for devchat lead next week

  • @sergeybiryukov has graciously volunteered to help with runnign next weeks Dev Chat, as many of us will be in transit for WordCamp US

Props to @clorith for helping lead devchat and write this summary. 🙌

#4-9, #4-9-1, #core, #dev-chat, #summary

PHP Meeting Recap – November 20th

This recap is a summary of this week’s PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

The meeting’s chat log.

Attendees: @flixos90 @jdgrimes @nerrad @overclokk @ptasker @schlessera @uofaberdeendarren @vizkr

Chat Summary

The agenda for this week was to finish the rest of the “Before Upgrading PHP” document that will be handed over to the marketing team afterwards to get their help with writing the copy.

Here is the discussion summary:

  • It was decided that the sections dealing with asking plugin/theme support, the hosting provider and possibly a developer for help should be combined into one help section at the end of the document. The reason for this decision is that all of those resources may or may not be available for a site owner, and the results of a consultation may vary. It should be emphasized that the upgrade steps are intended to be easy enough for the site owner to perform them on their own, but those resources should still be pointed out for those who feel more comfortable that way.
  • Merging those help sections into one has made the document more straightforward to read. It essentially now consists of the following steps:
    • Backup & Rollback Plan
    • Updates
    • Compatibility Check
    • Find replacements for incompatible plugins
  • The third step will hopefully become a lot simpler once the new WP Tide project is available.
  • The fourth step is at this point the least straightforward one. Finding plugin alternatives requires either good knowledge of the WordPress economy or an exhausting search. In addition, migrating from one plugin to the other will likely involve non-trivial tasks that only a developer could take care of. At least in regards to finding alternatives, a dedicated feature for that in the plugin repository could help. @schlessera pointed out that this is apparently already being worked on by the plugin repository team.
  • By the end of the meeting, it was agreed that the draft is now ready to be passed on to the marketing team so that they can build something awesome out of it. @flixos90 has since asked for their help in the #marketing channel.

Next week’s meeting

The next meeting will take place on November 27th, 2017, 16:00 UTC as always in #core-php. There is no scheduled agenda yet this time, as there hasn’t been a response by the marketing team yet. WordCamp US will however provide a good opportunity to talk about the document in person. If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account. See you next week!

#core-php, #php, #summary

Dev Chat Agenda for November 22nd (4.9.1 week 1)

This is the agenda for the weekly dev meeting on November 22, 2017 at 21:00 UTC / November 22, 2017 at 21:00 UTC:

  • 4.9 feedback + 4.9.1 planning
  • Request for devchat lead next week
  • 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-9, #4-9-1, #agenda, #dev-chat

Multisite Recap for the week of November 13th

Office Hours Recap

The agenda for this office hours meeting was to discuss adopting Trello as a way to manage status, progress, and ownership on tasks, as well as progress on multisite roadmap with a target to publish an initial version before WCUS.

The meeting’s chat log

Attendees: @desrosj, @flixos90, @jeremyfelt, @spacedmonkey, @vizkr

Chat Summary:

  • The full roadmap draft should be in place by November 21st, in order for the document to be published a week later, on November 28th, so that it is out before WordCamp US. @flixos90 and @jeremyfelt will have another look to complete the remaining sections.
  • After discussing possible usage of Trello in a collaborative way, the conclusion was that what is missing the most is an easy-to-use UI to manage required tasks and assignees for tickets on Trac. However most of the functionality is already in place and could be used through workarounds, so the decision was made not to use Trello for now. Instead the goal is to be more precise with defining tasks when assigning a ticket and generally assign tickets around between the responsible parties for a part of it more deliberately, instead of having a single owner through most of a ticket’s lifecycle. In a perfect world, there would be more possibilities to choose from when assigning a ticket to somebody, such as “update patch” or “write unit tests”, but for now these tasks can also be determined in regular comment text.

Next meeting

The next office hours will take place on November 21th, 2017, 17:00 UTC. Its agenda will be to review the roadmap draft and then discuss #42252.

Ticket Scrub Recap

No ticket scrub took place this week.

Next meeting

The next ticket scrub will take place on November 20th, 2017, 18:00 UTC. Its agenda will be to determine the current state and required tasks of tickets scheduled for 5.0 and assign them accordingly.

If you were unable to attend one of these meetings but have feedback, please share your thoughts in the comments on this post. In case there’s a need for further discussion we will ensure to make time for it in one of next week’s chats. See you next week!

#multisite, #networks-sites, #summary

PHP Meeting Recap – November 13th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

The meeting’s chat log.

Attendees: @flixo90 @jdgrimes @jon_bossenger @mikelking @mte90 @nerrad @schlessera

@sergey

Chat Summary

We started the meeting by examining the poll that @flixos90 had made regarding a modified meeting time slot.

As most of the votes went to the 16:00 UTC time slot, and nobody had a specific reason for not using that time slot, we decided to make that new time official from now on.

This means that all subsequent meetings are held at 16:00 UTC from now on.

Then we continued working on the “Before Upgrading PHP” section again, which we are working on in a shared Google Doc.

Here’s a brief summary of the corresponding discussions and decisions:

  • We discussed adding a second “Backup” step after all updates have been done. In case of a rollback further down the line, this would avoid going through all updates again, which incur a big time and bandwidth hit.
  • While discussing how to best add this addition “Backup” step, we came up with the idea of adding small “aside” text boxes to the document, which visually communicate that the content therein is not part of the critical path and should not be considered a blocker in case the user can’t complete that “aside”.
  • We discussed the different animals that Google Docs assigned to the anonymous users, and how they don’t seem to match up everywhere. 😉
  • Regarding the compatibility checker, we discussed whether to include knowledge about the future XWP project that might have an impact here, or not. We decided that we write the content for the current state and context, as there’s no guarantees to when or if any of the WIP projects will be completed and usable.
  • We added an aside to the compatibility checker as well, to warn users against false positives and other detection issues.
  • We acknowledged that our aside might be a bit on the intimidating side, and that we need the help of the #marketing team to rephrase the copy in that regard.
  • We rewrote the “Ask plugin/theme support” topic so that it is clearer and points people to existing resources first before contacting support.

Next week’s meeting

The next meeting will take place on Monday, November 20, 2017 at 16:00 UTC, as always in #core-php, and its agenda will be to finish the rest of the “Before Upgrading PHP” document that we will hand over to the marketing team to get their help with writing the copy. If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account. See you next week!

#core, #core-php, #php, #summary

Dev Chat Summary: November 15th (4.9 week 16)

This post summarizes the dev chat meeting from November 15th (agenda, Slack archive).

4.9 schedule + release timing

  • 4.9 release was delayed from yesterday (Tuesday, November 14th) to today (Wednesday, November 15th)
  • An updated 4.9 build went out earlier today, we still have to rebuild tinymce.min.js, but otherwise please test!
  • @afercia disagrees with patching last minute serious bugs without proper, broad, testing but deferred to decision by release leads
  • 4.9 release scheduled for later today (Wednesday, November 15th) at 3pm PST / 23:00 UTC
  • [Editor note: 4.9 released successfully! 🚀]
  • We’ll discuss post-4.9 / pre-5.0 plans later once we’ve had a chance to gather broader feedback on 4.9.
  • There is currently no timeline or plan for 4.9.x, but there are tickets currently slotted as 4.9.1 in Trac.

Meeting time changes

Gutenberg update

#4-9, #core, #core-js, #core-restapi, #dev-chat, #gutenberg, #summary

What’s New in Gutenberg? (15th November)

This next release includes several features and improvements on many levels. We are adding a way to switch between the header toolbar and toolbars attached to the block by opening the toggle menu at the top right and choosing the behaviour. There has been convincing arguments for both approaches so we want to make it easier to test both easily. Other notable features include the ability to transform multiple blocks of the same type into other blocks (like many images into a gallery). There are improvements to meta-boxes (dropping iframes), foundational work for nested blocks and global blocks, many design updates, and initial integration with JS hooks.

1.7 🐴

Other Changes

#core-editor, #editor, #gutenberg

Updated REST API meeting time

As with the other team meetings of late, this week brings a new time for the REST API team’s weekly meeting time! In light of the difficulty coordinating Asia/Pacific and US time zones we will be switching a bit later to 22:00 UTC on Wednesdays (22:00 UTC on November 15 this week), immediately following the weekly core dev chat.

Please note that this week’s meeting is liable to be light, as we encourage everyone to participate and dev chat and to pay attention to the planned 4.9 release! We’ll be meeting in full force again post-release next week to discuss plans for the next development cycle. 

Dev Chat Agenda for November 15th (4.9 week 16)

This is the agenda for the weekly dev meeting on November 15, 2017 at 21:00 UTC / November 15, 2017 at 21:00 UTC:

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-9, #agenda, #dev-chat

WordPress 4.9 final nightly build

As noted in the 4.9 release delay post, a final nightly build is now available for testing. This includes three commits, so please take a look through those and test as you can (see #42548, #42530, and #42545).

We hope to ship WordPress 4.9 on Wednesday, November 15th (that’s tomorrow) at 23:00 UTC, but we still need your help to get there. If you haven’t tested 4.9 yet, now is the time!

If you think you’ve found a bug, you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

We are almost there
But we still need help testing
So test, please and thanks!

Thanks for your continued help testing out the latest versions of WordPress.

#4-9