Tag Archives: summary

Francesca Marano 1:16 am on December 4, 2019
Tags: , summary   

WordPress 5.3 Retrospective Recap and Next Steps

The week of WP 5.3 release I posted a call for feedback for the development workflow.

Thank you to everyone that left their comments! Reflecting on what worked and what didn’t is a great way to move forward together and steer the wheel if and when needed.

Some comments didn’t follow the proposed format of start/stop/continue so it wasn’t very clear where they fit: I tried to put them in one of the categories. I also rephrased some feedback that was sometimes given as a positive statement (continue doing A instead of B) and sometimes a negative statement (stop doing B and do A). Finally, I added feedback I collected from the focus leads or from anonymous sources.

If something doesn’t feel right let me know and I will amend the post.

Read on for everyone’s feedback!

Continue reading →

#5-3, #summary

David Baumwald 10:56 pm on November 20, 2019
Tags: , , summary   

Dev Chat Summary: November 20, 2019

Here’s a summary of the November 20 Dev Chat (agenda / Slack archive).

Announcements

The 5.3 Retrospective – Call for Feedback post.

@clorith asked, “Would it be an idea to also allow for an anonymous form to submit to that? I know some folks may not be comfortable with the potential for conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved., and may feel safer giving an honest feedback if it wasn’t all public under their name? Then the feedback could be provided by the leads under a followup post, with no relation to individuals.”

@francina said she’d change the post to mention that anyone who’d like to give feedback privately is welcome to do so. 5.3 release leads @davidbaumwald, @youknowriad, @justinahinon, @audrasjb also committed to offering the same.

Upcoming Releases

5.3.1

@whyisjake offered the current list of tickets in the milestone at https://core.trac.wordpress.org/query?group=status&milestone=5.3.1

After a quick discussion of potential release dates, December 11, 2019 came out a potential winner. It’s pretty soon, but it still gives us time to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 5.3 regressions and bugfixes. That decision is not final – it’s pending more discussion in the comments.

Got thoughts on timing? Please leave them in the comments – the sooner the better.

While we see how those conversations shake out, @audrasjb graciously offered to lead the first 5.3.1 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. scrub on Thursday November 21, 2019 18:00 UTC

Next up: a call for volunteers to lead the release.

@sergeybiryukov, @audrasjb, @amykamala, @marybaum, and @whyisjake all raised their hands. Everyone expressed great confidence in the potential candidates.

Want to be part of the 5.3.1 release squad? Please leave a comment.

Open floor

@youknowriad brought up a discrepancy in the release cadence between WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/:

By December 11, the date proposed for a 5.3.12 release, Gutenberg will be ahead of Core with about 5 releases and this is a problem. 12 Gutenberg releases shipped into 5.3 . This is too much for a single WordPress release and with the current schedule, it’s seems like this is going to be similar for 5.4. This is not tenable for the future. It’s hard to stabilize and ship, it’s hard to summarize the changes for third-party [developers] and users, it’s more scary to ship and people were recommending the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to be installed for their clients (and it’s risky since the plugin is a development plugin). So how to reduce that gap is a big issue that needs solving IMO.Ideally I do think a shorter release cycle for majors is better. (Why not just a 5.4 in like end of January). [O]therwise we’ll have to include enhancements in minors.

This generated a long discussion that continued well past the end of the Dev Chat. See the full conversation starting here.

@davidbaumwald led the chat and wrote these notes. @marybaum did some editing.

#5-3, #dev-chat, #summary

David Baumwald 9:04 pm on October 23, 2019
Tags: , , , summary   

Dev Chat: 10/23/2019

The facilitator for this week’s chat was @audrasjb.

Announcements

WordPress version 5.3-RC2 was released on Tuesday. Everyone please help by testing out the 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 latest Dev Notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. published for 5.3 discuses “Noteworthy Adminadmin (and super admin) CSSCSS Cascading Style Sheets. Changes in WordPress 5.3”.

Also, the official Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. for 5.3 was published!

@audrasjb called attention to the wonderful documentation work this cycle by @justinahinon and @jeffpaul. Thank you to both for their extraordinary efforts!

5.3 Updates

@azaozz Pointed out that there are only two tickets needing work after RC2, excluding the About Page. Follow the ticketticket Created for both bug reports and feature development on the bug tracker. progress in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. here.

@ianbelanger informed the group that there are currently 0 tickets in the Bundled Themes component for Twenty Twenty. However, he added that an RC3 release would be helpful.

@audrasjb brought up ticket #48396 regarding @afercia‘s request to revert two lines of CSS to remove an unwanted changes on disabled buttons. @azaozz confirmed the revert to be a minor one and suggested that it move forward based on testing.

A pre-RC3 Bug Scrub in the #core channel was tentatively scheduled for Monday October 28, 2019 15:00 UTC. If there are no new tickets or regressions reported prior, the scrub will not take place.

@sergeybiryukov asked about branching for 5.3 this week. @peterwilsoncc suggested certainly branching before WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., as to allow for good-first-tickets to be committed for new contributors. @desrosj added that branching could be done at any time now that the dust has settled from RC2, but deferred to @azaozz‘s judgement as CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead for 5.3. @azaozz suggested trying to resolve a couple of remaining issues in 5.3 prior to branching in the next few days, and a consensus was reached around this idea.

These notes were taking by @davidbaumwald and proofread by @audrasjb

#5-3, #dev-chat, #summary

marybaum 4:43 pm on October 21, 2019
Tags: , , , summary   

Dev Chat Summary, October 16, 2019

@francina led off a well-attended dev chat – 29 active participants! – with the standard introduction and remarked that we were in Week Nine of the release cycle.

Announcements and Highlighted Posts

She issued a call for announcements and highlighted posts, then announced that WordPress 5.3 Release Candidaterelease 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). 1 had landed the day before, on October 16.

@azaozz and @sergey were our packagers; @francina and @desrosj led the process.

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.

@johnbillion called the group’s attention to a crop of new dev notes as a way to keep up with changes in 5.3 for devs; @justinahinon linked to the 5.3-specific ones here.

@jeffpaul added that pending one more dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. will publish shortly.

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) testing in the 5.3 Adminadmin (and super admin)

@francina directed the group to this report from @audrasjb on accessibility testing of the CSS changes coming to 5.3 against the 20 most popular plugins on the WordPress.org repository.

@francina thanked @jeffpaul for the Field Guide and @ipstenu for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party support.

Upcoming Releases

5.3

@francina‘s call for updates prompted mostly murmurings that everything’s progressing on schedule. @azaozz pointed out there were only a couple of new tickets after RC1, and @desrosj had three to call out for reviews from other committers: #48022, #48312, #47699.

(Remember that after RC1, every commit needs signoff from two committers, not one, until launch.)

Discussion of a related ticketticket Created for both bug reports and feature development on the bug tracker., #48331, followed.

Calls from Component Maintainers

@francina opened the calls from component maintainers.

@jeffpaul: Not a component maintainer update, but worth noting that during the RC1 packaging process (I believe) we confirmed that trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. would be opened back up after RC2.  That may be worth confirming here and noting in the devchat summary post which you’re reading now)

@sergey and your faithful but tardy reporter confirmed that we’ll start milestoning for 5.4 at that point, and @desrosj pointed the group to the RC1 discussion here.

The final announcement from @davidbaumwald was this:

@committers Committing to Core is now open again.  Reminder, now that we’re in RC, the dev-feedback and dev-reviewed workflow is required prior to committing, where each commit must get double-signoff.

@desrosj pointed out that 5.4 already has 94 tickets. He encouraged the group and observers (and you, dear reader!) to address these 94 tickets first or puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) them if they’re unrealistic.

Open Floor

@francina had two items.

RC2

RC2 is tomorrow, October 22. @francina asked the group for a team and a timeline; discussion followed about some last-minute changes that we won’t be making tomorrow.

Workflow for the About Page

@francina also opened the floor to a discussion about whether or not the About Page can get locked down 24 hours before a release. For the most part, the group agreed that much of the page can, but there will always be a few last-minute fixes — especially for majors.

See you tomorrow for the launch of RC2!

#5-3, #core, #dev-chat, #summary

David Baumwald 9:50 pm on October 9, 2019
Tags: , , , summary   

Dev Chat: 10/9/2019

@davidbaumwald served as facilitator and note taker for this week’s chat held in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. To view the chat from the beginning, click on this Slack Archive.

Announcements

WordPress version 5.3 Beta 3 was released on Tuesday. Congratulations to everyone involved in inching 5.3 closer to the finish line.

5.3 Updates

With 5.3 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. 3 now release, focus turns to Release Candidaterelease 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). 1(RC1) is next on the schedule just a few days from now. A “soft string freeze” is now in effect.

@francina called for volunteers for next week’s RC1 release session. Both Mission Control(MC) and a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. will be required. @azaozz and @sergeybiryukov raised their hands.

@karmatosed provided a quick update on 5.3’s About page, saying that everything is on track and copy is being finalized.

@jeffpaul inquired about the progress on compilation of Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 5.3. @justinahinon pointed to a Google Sheet that he’s using to organize them and coordinate volunteer authors.

This discussion led to a call for more volunteers and ticketticket Created for both bug reports and feature development on the bug tracker. owners to draft Dev Notes. @desrosj mentioned that he’s “… started a page for the handbook collecting the learnings from the last three releases for this.”

@ianbelanger brought a Twenty Twenty update to the group. A PR has been opened to address WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. violations in the Beta Twenty Twenty 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., and a call for testing was announced. @karmatosed added that testing on mobile is a great help to the team.

Open Floor

@azaozz mentioned that there are, as of writing, only 37 open tickets in the 5.3 milestone, and everything should be closed out as RC1 is released. This was a great reminder of the tremendous work done by Core ContributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. during the course of the 5.3 cycle, as over 350 tickets were initially open when the cycle was kicked off!

These notes were drafted by @davidbaumwald and proofread by @justinahinon.

#5-3, #dev-chat, #summary

Justin Ahinon 4:57 pm on October 4, 2019
Tags: , , summary   

Dev Chat summary: October 2

The 5.3 Release Coordinator, @francina, led the chat (full transcript). For the record, here was the agenda for the meeting.

Announcements and highlighted posts

@francina made some announcements and pointed out highlighted posts from Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site):

Feel free to browse through these posts and add comments or thoughts.

@youknowriad mentioned Gutenberg 6.6 recap post. This version focused on stability for the editor and performance for WordPress.

Upcoming Releases

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ team lead @youknowriad said they welcome any testing to detect bugs and regressions before 5.3 release. You can see what’s happening with the editor on this GitHub board.

Site Health component maintainer @clorith reported that desired changes are on track and should be ready for the Release Candidaterelease 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)., currently scheduled for October 15.

Docs coordinator @justinahinon said 5.3 dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. include some for major changes/enhancements, plus many others. Check out all the dev notes here.

@earnjam reminded the group that each published dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. on Make/Core sends an email to ~4000 newsletter subscribers. He suggested authors limit each dev note to a single topic so people can find things in the index.

@francina shared WordPress 5.3: Accessibility focus progress report.

WordPress project Executive Director @chanthaboune brought up changes that are coming to the adminadmin (and super admin) interface. She stated that the focus leads have been discussing whether to keep the changes or allow extra exploration time for them, as suggested in this post.

Here are the key stances she noted from the various discussions so far:

  • There are some concerns about how quickly the changes were decided on and then implemented from design.
  • There are some concerns raised about the process overall, and whether there’s enough time for testing. Josepha and a few core committers share this concern.
  • There are concerns that further delays will result in loss of momentum from 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) as well as confidence in an iterative process.

Josepha said she’s doing her best to balance progress with caution, and that she has gotten a lot of feedback from the release focus leads.

Here are the different opinions that have been shared by people regarding this:

  • @garrett-eclipse said that when the changes landed in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. with several bugs popping up all over, he was leaning towards the pull, but now that the team seems to have addressed and crushed the majority of them, he’s more in favor in keeping the changes.
  • @clorith reminded that while they are worth doing, he agrees on the fact that the changes may have come a bit late in the cycle with limited time for testing and exposure.
  • @mapk asked if the a11yAccessibility 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) improvements at the cost of design worth immediate and rapid merging, or if we can take the time we need to fully test and address issues?
  • @samuelsidler asked about the items of concerns/tasks that can not or will not be fixed before 5.3 Release Candidate.
  • @melchoyce answered @samuelsidler about tasks that can’t/won’t be fixed before 5.3 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).:
    • Wider design changes to account for the shift in the hierarchy; because the new form fields are so much darker than the list tables, any page where both exist is thrown off a little.
  • @mapk answered @samuelsidler saying that he believes there are other design explorations to address and a committed testing cycle for a large release.
  • @karmatosed answered @samuelsidler and said that the design team has an experiment pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to use for that.
  • @karmatosed shared some worries she has about this:
    • Documentation: those that write tutorials and might find their screenshots out of date.
    • Testing: A longer testing phase for her would be better just like during mp6 project. She thinks that 5.4 should be a focused release, with testing, time and iteration feel safer.
  • @joemcgill said that since he has not been part of the discussions, he would be more concerned by process problems keeping a11y improvements from shipping rather than shipping changes that improve a11y and then iterating on the design.
  • @afercia clarified that most of the design changes come from design and were implemented on top of the a11y improvements. He also mentioned that from an a11y perspective all the matters are:
    • Removing the fixed heights from the input fields etc.
    • Improving contrast
  • He also said that all the other changes are unrelated to a11y and came from design feedback.
  • @samuelsidler asked @melchoyce if there is a plan in place to fix/iterate on those visual issues for the future? If yes, when in the future? He also asked if those improvements happen in 5.3.x or they would need to be in 5.4 or later?
  • @melchoyce replied to @samuelsidler and said that he thinks they would be wide-reaching enough that the design team would need to ship them in 5.4.
  • @earnjam expressed that he would personally lean toward a more cautious approach and allowing further iterating as a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. with an earlier merge in a release cycle to allow more time to catch/fix the bugs. He also feels like we’re trading one set of bugs/issues for a different set and doing it during the 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. period.

This discussion has continued with different arguments from design and a11y team members and with other contributors as well. You can read the discussion in its entirety here.

Calls for components maintainers have been skipped for this chat.

Open Floor

@azaozz noted that he’s started to get concerned by the 100+ tickets that are still open for 5.3. He invited maintainers and committers to review and comment on tickets that must be in the release and move the rest to the Future Release milestone.

@afercia said that while the a11y team is committing a lot of things, they will need urgent feedback on #47069 and #43037. @ryokuhi gave a brief explanation about the last ticketticket Created for both bug reports and feature development on the bug tracker..

@davidbaumwald said he’s planning a last-minute scrub due to the high number of tickets that are remaining for 5.3. The schedule for 5.3 scrubs can be found here. Again, everyone is welcomed to attend scrubs and also to organize them.

@justinahinon shared a “Special interest” he has about developer documentation, dev-notes, and WordPress codebase. You can read about it on the chat agenda comments.

@davidbaumwald reminded that they will be doing a lot of punting at the end of the week, so two things:

  • If you have a ticket you absolutely want in 5.3, get moving.
  • If not, at least leave a comment on feasibility for 5.4, or he’ll be moving everything to Future Release if they haven’t seen any movement in a while.

@desrosj clarified that the tickets owned by committers and maintainers have largely been left in the 5.3 milestone to allow those owners to make the decisions they feel are appropriate. If those tickets are not gardened in the next few days they will be punted.

Finally, @azaozz added that the best would be the component maintainers to decide what is good to be in 5.3 and what is going to be in 5.4 of future releases.

That’s the end for this long, lively and important devchat.

#5-3, #dev-chat, #summary

Justin Ahinon 3:37 pm on September 26, 2019
Tags: , , summary   

Dev Chat summary: September 25

As our Release Coordinator @francina was not available yesterday, @mapk led this chat. Thanks to all the attendees.

Announcements and highlighted posts

First announcement was Beta 1 of WordPress 5.3 that went out earlier this week. Every one is invited to help test it and report bugs and unexpected behaviors. The 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. includes the first iteration of Twenty Twenty, the new default theme which development is ongoing on GitHub.

Here are some highlighted posts shared by @mapk:

@antpb also shared the Media component weekly report.

Upcoming Release Discussions

@mapk said GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ team started a project board in the editor GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for the issues and pull requests that they’re hoping to get in or at least backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. into 5.3.

Twenty Twenty lead @ianbelanger said the team is particularly looking for help on this issue.

@audrasjb made a post-Beta1 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) update focus. 6 important tickets for the focus where committed just before the release. They are still 33 open tickets in the milestone. Everyone is invited to help tackle them and join the focus weekly 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. scrub every Friday at 2 PM GMT+3.

@davidbaumwald remembered that there are dedicated bug scrubs for 5.3 with the schedule here which Beta 2 is scheduled for next Monday.

@desrosj noted that 5.3 Release Candidaterelease 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). 1 is scheduled for October 15, and that the list of remaining tickets in the milestone needs to be empty by this date.

Calls from component maintainers

@audrasjb pointed out the 15 ready to be committed tickets in 5.3 milestone and asked for available committers attention on them.

Open Floor was quiet yesterday. And the chat ended up under one hour at 9:40 PM.

#5-3, #dev-chat, #summary

Justin Ahinon 11:05 am on September 22, 2019
Tags: , , summary   

Dev Chat summary: September 18

@francina was the chat leader. Archives for the chat can be found in #core on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Announcements

@francina shared a devnote by 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) team. We also had an update from @audrasjb from Accessibility team who said they are working on creating accessibility devnotesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 5.3.

Upcoming Release Discussions

@ianbelanger gave an update of the work on default theme Twenty Twenty. A working version of the theme will be available on Monday 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. 1 of WordPress 5.3. The development of the theme is happening on GitHub and contributions are more than welcome on the repository or in #core-theme channel on Slack.

@audrasjb make an update for Accessibility focus for 5.3. He remembered that they have 2 dedicated scrubs per week and that the team is currently coordinating with the Design team to determine which changes will be included in 5.3.

@jorbin gave an update for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 7.4 in WordPress. All the changes for the version are already landed in trunk. He also highlighted the great work of @desrosj and @jrf to make this possible. He finally announced the target is to fully support PHP 7.4 with WordPress 5.3.

@desrosj made a call for help for tickets in this report on WordPress TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. People who own tickets in that report are invited to give them a status and to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) them if they feel that the tickets will not be ready for 5.3 release. Also owners who are not anymore available to continue working on their tickets are invited to remove themselves as owner and leave a status so that another contributors can take the relay.

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/. component maintainer @kadamwhite announce that the team is about to land a good set of enhancements before the Beta 1 deadline. Dev-notes for these changes will be published soon of Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site).

@garrett-eclipse from Privacy team announced that 4 privacy related enhancements have already been included for the release with no issues.

@antpb made an update for Media component, and remembered that the focus for the the release is around image handling and UIUI User interface improvement and accessibility issues. Tickets for the focus can be found on WordPress Trac here.

5.3 Marketing Lead @mikerbg announced that the marketing team is working to organize content for the about page and other assorted release announcements. Progress on their work is tracked here.

@davidbaumwald remembered that scrubs schedule for 5.3 can be found here and that @marybaum volunteered to lead the one of October 9. Scrubs take place on #core channel on Slack and anyone interested in welcome to participe or to run scrubs.

Calls from component maintainers

@kadamwhite said 5.3 is probably the best release for REST API improvements in a long while, and that the team is grateful for everybody who has contributed to the component.

Open floor

@ianbelanger said Twenty Twenty team have been discussing the idea of having a demo site for the theme asked if this is something that can be done, and what happened for previous default theme. @kraftbj volunteered to help on this.

@kadamwhite asked for another persons eyes on #42094.

@garrett-eclipse asked help for review from available committers on #37782 before Monday.

@audrasjb pointed out #46312, a candidate for an easy commit action.

@hareesh-pillai asked for movements on https://meta.trac.wordpress.org/ticket/4706 as it is a blockerblocker A bug which is so severe that it blocks a release. on #22994.

#5-3, #dev-chat, #summary

Josepha 8:46 pm on September 4, 2019
Tags: , , , , summary   

Dev Chat Summary: September 4

@audrasjb was our chat leader today and did an excellent job as usual. (backscroll)

Announcements

JB shared some posts that are currently open for discussion, feedback, or volunteering.

  • About page design: https://make.wordpress.org/design/2019/08/28/discussion-about-the-about-page/
  • New feature plugin proposal: https://make.wordpress.org/core/2019/09/04/feature-plugin-proposal-privacy-data-request-form/

Upcoming Release(s) Update

  • WordPress 5.2.3
    • This is due out today!
    • Right after devchat the plan is to begin the final packaging and release process.
  • WordPress 5.3 has a new batch of focus leads!
    • @miker joined the team as Marketing Focus Lead
    • @ianbelanger joined the team as Default Theme Wrangler
    • @andersnoren joined the team as Default Theme Designer
  • WordPress 5.3 also has an updated timeline posted here: https://make.wordpress.org/core/5-3/
  • All bug scrubs are listed here: https://make.wordpress.org/core/2019/08/27/bug-scrub-schedule-for-5-3/ . The next general bug scrub is Sept 5, 2019 at 14:00 UTC in #core channel.

Call for Component Maintainers

  • @azaozz has put up a challenge to his fellow maintainers for 5.3 (and hopefully beyond!) https://make.wordpress.org/core/2019/08/30/component-maintainers-in-5-3/
  • @chanthaboune shared that the maintainers of the default themes are due for a change
    • @ianbelanger and @williampatton raised their hands to help with that transition.
    • @clorith suggested it’s time to have a clearer support plan for working with default themes

Open Floor

  • If anyone is local to the Orlando area, there’s a community event coming up. https://www.meetup.com/WordPress-Orlando/events/263847409/

Important WP5.3 Dates

  • September 23: 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 (begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and About page, and last chance to merge feature projects)
  • September 30: Beta 2 (continue writing Dev Notes and About page)
  • October 7: Beta 3 (continue writing Dev Notes and About page, and soft string freeze)
  • October 15: Release candidaterelease 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). 1 (publish Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. with Dev Notes, commit About page, begin drafting release post, and hard string freeze)
  • October 22: Release candidate 2 (update About page images, and continue drafting release post) (also @audrasjb‘s birthday!)
  • October 29: Release candidate 3 (update About page images, and continue drafting release post)
  • November 5: Release candidate 4 (if needed)
  • November 11: Dry run for release of WordPress 5.3 and 24 hour code freeze.
  • November 12: Release Day!

#devchat #summary #5-2-3 #5-3

#dev-chat

Josepha 9:57 pm on August 14, 2019
Tags: , , , , , summary   

Dev Chat Summary: August 14

After the close of our every-two-weeks new contributor chat, the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. chat started at 2000 UTC, give or take a few minutes. (backscroll)

Announcements

Next Minor: 5.2.3

Next Major: 5.3

  • All but two focus lead type people are settled. An update post is upcoming (and will be shared by the end of the week regardless of whether those final two are settled or not).

Open Floor

To Do List from this Chat

  • First 5.2.3 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. scrub Thursday, August 15 @ 1700 UTC
  • If you want to help with the 5.2.3 minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. and weren’t mentioned above, you can indicate your interest in the comments of this post.

#summary #5-2-3 #5-3 #rest-api #auto-update