Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
woocommerce/docs/quality-and-best-practices/review-guidelines/notifying-users-about-impor...

19 lines
1.5 KiB
Markdown
Raw Normal View History

Create Review Guidelines documentation page, and fix a typo. (#50248) * Fix typo Fixed one typo * Create reviews-guidelines.md Creating the first draft of the Operation Star guidelines for partners to improve reviews and ratings. * Adding more info and feedback! adding info from https://wooengineering.wordpress.com/2024/07/30/closing-the-loop-enhancing-product-reviews-through-integrated-feedback/ * Update docs manifest * Update menu_title for consistency * Standardize language + remove unsupported characters from review doc * Atomize review docs into subcategory + subpages * Fix linting issues * Update docs manifest with linter fixes --------- Co-authored-by: Jacklyn Biggin <hi@jacklyn.dev>
2024-08-22 21:05:51 +00:00
---
Fix typos/special chars in Operation Star docs (#50894) * Fix typos/special chars in Operation Star docs * Update docs manifest * Fix remaining special characters
2024-08-23 14:43:07 +00:00
post_title: Notifying users about bug fixes and feature requests
Create Review Guidelines documentation page, and fix a typo. (#50248) * Fix typo Fixed one typo * Create reviews-guidelines.md Creating the first draft of the Operation Star guidelines for partners to improve reviews and ratings. * Adding more info and feedback! adding info from https://wooengineering.wordpress.com/2024/07/30/closing-the-loop-enhancing-product-reviews-through-integrated-feedback/ * Update docs manifest * Update menu_title for consistency * Standardize language + remove unsupported characters from review doc * Atomize review docs into subcategory + subpages * Fix linting issues * Update docs manifest with linter fixes --------- Co-authored-by: Jacklyn Biggin <hi@jacklyn.dev>
2024-08-22 21:05:51 +00:00
menu_title: Notifying users about bug fixes and feature requests
---
A bug or a missing feature can be a showstopper for merchants. Bugs that pile up or popular features that are not implemented can lead to negative reviews and/or merchants churning and looking at a competitive solution.
Bugs are usually reported via support or GitHub, or you can discover them yourselves in testing.
When a critical bug is found, resolve it within a couple of days (most critical bugs should be resolved within 24 hours) and release a new plugin version promptly. Part of your release process should be to notify all stakeholders (the support team and the merchant affected) about the upcoming release.
Fix typos/special chars in Operation Star docs (#50894) * Fix typos/special chars in Operation Star docs * Update docs manifest * Fix remaining special characters
2024-08-23 14:43:07 +00:00
Even though a critical bug is a great source of stress for merchants, a quick resolution makes merchants feel heard and supported - having a reliable business partner, who is keen to help in the most difficult situation, helps build a stronger relationship. Therefore, we usually ask merchants for a 5* review when we deliver a fast solution.
Create Review Guidelines documentation page, and fix a typo. (#50248) * Fix typo Fixed one typo * Create reviews-guidelines.md Creating the first draft of the Operation Star guidelines for partners to improve reviews and ratings. * Adding more info and feedback! adding info from https://wooengineering.wordpress.com/2024/07/30/closing-the-loop-enhancing-product-reviews-through-integrated-feedback/ * Update docs manifest * Update menu_title for consistency * Standardize language + remove unsupported characters from review doc * Atomize review docs into subcategory + subpages * Fix linting issues * Update docs manifest with linter fixes --------- Co-authored-by: Jacklyn Biggin <hi@jacklyn.dev>
2024-08-22 21:05:51 +00:00
When you implement a new feature request and ship a new plugin version, you can follow a similar approach to bugs:
* Notify all stakeholders.
* Update the relevant request in the Feature Requests board, by sharing a public update and marking it as 'Completed'.
* For breaking releases: communicating with your marketing/relations teams to publish updates/newsletters before the release.