Issue Triage
Issue Triage Process
To ensure that our weekly WordPress contributions are effective and impactful, we follow a structured triage process. This allows us to categorize incoming feedback, prioritize critical fixes, and maintain a high standard for our MVP-derived codebase.
Categorization
Every issue submitted to this repository is categorized into one of three primary buckets to determine the necessary workflow:
- Bugs: Reports of unintended behavior, regressions, or broken functionality within the WordPress environment or our custom implementations.
- Enhancements: Requests for new features, UI improvements, or optimizations that extend current functionality.
- Maintenance: Tasks related to documentation, dependency updates, or code refactoring that do not directly change user-facing features.
Labeling Conventions
We use a standardized labeling system to provide immediate visual status updates on any issue. You can track the progress of your submission by monitoring these labels:
| Label | Description |
| :--- | :--- |
| status:triage | The issue is new and awaiting review by the maintainers. |
| type:bug | Confirmed technical issue that requires a fix. |
| type:enhancement | A request for a new feature or improvement. |
| priority:high | Critical issues affecting core site functionality or security. |
| status:needs-info | More context (logs, screenshots, or environment details) is required from the reporter. |
| status:accepted | The issue has been vetted and is scheduled for development. |
Priority Levels
Prioritization is determined based on the impact on the WordPress ecosystem and our current MVP requirements.
1. High Priority (P0/P1)
Issues that cause site crashes (White Screen of Death), data loss, or security vulnerabilities. These are addressed immediately.
- Example: A plugin conflict that prevents the WordPress admin dashboard from loading.
2. Medium Priority (P2)
Functional bugs that have a workaround or minor feature requests that align with our current development roadmap.
- Example: A custom block not rendering correctly on specific mobile browsers.
3. Low Priority (P3)
Cosmetic tweaks, non-essential feature requests, or minor documentation updates.
- Example: Updating a description in the
README.mdor adjusting CSS padding on a non-critical element.
How to Submit an Issue
To expedite the triage process, please use the following structure when reporting a bug. This ensures we have the necessary data to replicate the issue without back-and-forth communication.
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Environment Details**
- WordPress Version: [e.g. 6.4.1]
- PHP Version: [e.g. 8.1]
- Browser: [e.g. Chrome, Safari]
Response Timeline
Since we make contributions on a weekly basis, new issues are typically reviewed every Tuesday/Wednesday. During this time, we apply labels and assign tasks for the upcoming development sprint.