Version 3.0+ Disaster
-
From 2.6.4 to 3.0+ is a whole disaster! If you did not make enough test why did you publish 3.0? Since the beginning of April, every week an update comes, we are tired and Themes-Plugins are living nightmare. Shame on you!
-
https://woocommerce.wordpress.com/2017/04/04/say-hello-to-woocommerce-3-0-bionic-butterfly/
>As always, before upgrading ensure that your extensions and theme are compatible with 3.0 and you’ve made backups. If unsure, check with the theme/extension developer.
>
>Store owners, read this helpful guide on preparing for the update and if you see any deprecation notices after updating don’t be alarmed; read here to understand why.And:
>In total we had 4 beta versions for “2.7” from December; you can check out the Beta 1, beta 2, and beta 3 posts if interested. We then had a “2.7” release candidate before deciding to move to Semantic Versioning and use 3.0.0 instead. In total our betas have had at least 1,148 downloads according to the stats we have from Github.
>
>Internally we’ve been testing our own plugins and themes, releasing updates where needed, and we’ve had support from our 3rd party developers also. Huge kudos to our 3rd party devs!
>
>On top of the manual testing we’ve all been performing, and the testing by the community, we’ve also been gradually expanding our unit test coverage which is now up to 50%. You can view current test coverage on Scruitinizer.Extension developers and testers have been on it since December. 4 months is ample warning for devs.
- The topic ‘Version 3.0+ Disaster’ is closed to new replies.
