Thanks to everyone that joined us today for the twenty-fourth installment of the WooCommerce Dev Chat. Based on emoji reactions, we had about 20ish people in attendance ( inflated a bit because I imagine there were some lurkers )! You are welcome to read the full backscroll of the dev chat here, or find some notes after the break.

Follow-Up Items

We spent the first bit of the talk going over a couple of questions that came up during the end of Dev Chat #23:

When will the Trello board be updated?

The Woo Trello board should be updated within the next few weeks.

What is the best way to suggest new features or enhancements?

If you have an idea for an enhancement or feature suggestion, please open up an issue in the repository, and apply the “Votes Needed” label. And we had another follow up question on this topic:

how far along is best for these new feature ideas, in terms of implementation? Is opening the issue more to start a discussion and determine if the idea should be pursued, as opposed to coming in with a PR straight away?

@chasewiseman

to which Mike replied:

If you have code ready then I see no issue with submitting a draft PR for feedback. But if you need feedback first, i.e. you need some input on direction, using the enhancement template is probably the best first step.

@mikejolley

3.6

The next item on the agenda was discussion around the next release of WooCommerce. We are aiming to hit the following dates for the release cycle:

Beta~ March 7
RC~ March 21
Release~ April 2

3.6 Features

The following is a list of features slated for the release. You can also view the PRs that are in progress, or already merged to the milestone here.

On the Performance Improvements front, @rodrigosprimo asked for any developers who are having performance issues currently to reach out if they can:

I just would like to add that as part of our performance work, would be great if we could get in contact with developers running WC stores that are struggling with performance. So please ping me or anyone else on the team if that is your case.
Specifically, performance issues caused by WC core.

Google Schema Warnings

The final item discussed during the meeting was some recent issues reported around Google Schema warnings on archive pages. A few insights on the topic were shared, but we all agreed that a bit more research should be done on the matter. Please do read up on the issue here and feel free to chime in with other feedback there.

Till Next Month!

Thanks again to all whom attended. If you have any ideas on how to make dev chats more helpful, or if you have a question/topic you would like to discuss, please leave a note in the comments below.