-
Notifications
You must be signed in to change notification settings - Fork 235
Labelling Issues
Rémy Perona edited this page Nov 6, 2019
·
1 revision
Labels are used on issues and pull requests to identify:
- The related module in WP Rocket
- The type of issue (new feature/enhancement/bug)
- The severity of the issue in case of a bug
- The status of the issue
- Some other useful indicators
You'll find below the list of labels for each category and an explaination of it's purpose.
-
module: browser cache- for issues related to our browser caching features, mainly htaccess rules for Apache -
module: cache- for issues related to our cache feature -
module: CDN- for issues related to our CDN feature -
module: cloudflare- for issues related to our Cloudflare Add-On -
module: dashboard- for issues related to our dashboard tab on settings page or the general WP admin area -
module: database- for issues related to our database optimization feature -
module: Facebook Pixel Add-On- for issues related to our Facebook Pixel Add-On -
module: file optimization- for issues related to our file optimization features: HTML/CSS/JS files -
module: Google Tracking Add-On- for issues related to our Google Tracking Add-On -
module: heartbeat- for issues related to our Heartbeat control feature -
module: lazyload- for issues related to our lazyload feature -
module: logger- for issues related to our debug log feature (in development) -
module: media- for issues related to our media features: Emojis, Embeds, WebP -
module: preload- for issues related to our preload feature -
module: sucuri- for issues related to our Sucuri Add-On -
module: tools- for issues related to our tools tab on the settings page -
module: Varnish- for issues related to our Varnish Add-On
-
feature request- for requests of new features in the plugin -
type: bug- for issues identified as a bug to be fixed -
type: enhancement- for issues concerning an improvement of something existing in the plugin -
type: new feature- for issues concerning a new feature of the plugin
-
severity: critical- for issues that are breaking the plugin (Fatal error for example) -
severity: major- for issues that are impacting a large number of our users -
severity: minor- for issues that are impacting a small number of our users, or on very specific area -
severity: trivial- for issues that are impacting a very small number of our users, or typography mistakes
-
help wanted- an issue currently blocked because the assigned contributor needs help on it -
duplicate- for opened issues that are a duplicate of an already opened one -
invalid- for issues that are not appropriate for the plugin -
needs copywriting- for issues that needs work on copy before continuing -
needs design- for issues that needs design work before continuing -
needs testing- for issues that needs testing to determine if they are valid/how to resolve them -
triage- for issues that needs to be reviewed to determine if they are still valid -
waiting for feedback- for issues that needs feedback before continuing -
wontfix- for issues that we won't fix
-
3rd party- for issues or compatibilities related to another product (hosting/plugins/themes) -
Beacon- for issues related to HelpScout Beacon integration -
community- mainly used for pull requests submitted by our users -
design- for anything touching the design, mostly in the settings page area -
good first issue- for issues that are good as a starting point to contribute to the plugin -
i18n- for issues related to internationalization in the plugin -
multisite- for issues related to WP multisite -
Onboarding- for issues related to the onboarding process (TBA) -
question- for issues that are not a problem, but a question about how something works for example