Categories
Core

May 2nd: Dev Chat #26

We are resuming our dev chats after the release of WooCommerce 3.6. Our last dev chat was on March 28th, and now it’s time to get back to our regular schedule.

The next chat will be on Thursday May 2nd at 16:00 UTC in the #core channel of the WooCommerce Community Slack. If you don’t already have access to the group, you can request an invite here.

In this devchat we’ll like invite everyone to talk about WooCommerce 3.6, let’s do a retro and talk about what went well and what didn’t, new features, performance improvements, bugs and so on.

As always – if you have any other questions, or topics you would like to chat about during Dev Chat #26, please drop a comment below.

See you all!

By Claudio Sanches

Developer on the WooCommerce team and member of the WordPress Brazilian community.

5 replies on “May 2nd: Dev Chat #26”

I have a question as a store owner who makes his own sites and deals with the upkeep. The recent, rapid updates made me (and others) nervous. Everything went smoothly for my site, but in my WooCommerce group some people are reporting issues and saying that the store owners were the beta test group. Can the developers make a statement that speaks to people like me, that gives an overview in not too technical language as to what prompted the first update to 3.6 and then why the issues that cropped up required the subsequent releases?

Liked by 1 person

Can the developers make a statement that speaks to people like me, that gives an overview in not too technical language as to what prompted the first update to 3.6 and then why the issues that cropped up required the subsequent releases?

This is almost the subject of this dev chat, you can feel free to join, we call “dev chat”, but it’s most just fine for store owners too, it’s a good place to suggest changes and give feedback.

The recent, rapid updates made me (and others) nervous. Everything went smoothly for my site, but in my WooCommerce group some people are reporting issues and saying that the store owners were the beta test group

I complete understand, and I’m glad that you haven’t been affected with any of those issues.

So we released 3.6 including a few performance improvements, also including a patch to prevent multiple cookies been set per request that didn’t work so well in a few servers (with a specific PHP function that have a bug in some configurations, sorry, but this one it’s really technical), that’s why we released 3.6.1 so quickly (hours after we released 3.6.0) to help users on servers that are experiencing this problem, there’s more details in https://woocommerce.wordpress.com/2019/04/18/woocommerce-3-6-1-release/.

And then a few days later we released 3.6.2 including more fixes and improvements for performance, also fixing a bug with themes, looking at the changelog (link bellow) you can see that we have not only fixes for 3.6.x, you can also find some fixes that are reported before 3.6 has been released, but we couldn’t include any of those fixes, since we need to stop including new code when close to the release (happens when we hit the Release Candidate stage, in this stage we stop including new code, so people everyone can test consistently), and of course, none of those fixes are critical, that’s we included into 3.6.2. You can find more details in https://woocommerce.wordpress.com/2019/04/24/woocommerce-3-6-2/.

I hope that this summary may help you. Feel free to ask questions and join the dev chat.
Thanks.

Liked by 2 people

do you guys usually post the chat Summary ?

Yes, we post summaries from each dev chat, you can find all posts related to dev chat in https://woocommerce.wordpress.com/tag/dev-chat/

Curious to know what is planned for 3.7

We haven’t discussed idea plans for 3.7, but this is something that we should target in the next dev chats.

Like

Comments are closed.