Update bug report template to identify the editor version better #21564
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jorgefilipecosta
added
the
[Type] Project Management
jorgefilipecosta
requested review from
karmatosed,
mapk and
youknowriad
as code owners
|
Size Change: -63 B (0%) Total Size: 839 kB
ℹ️ View Unchanged
|
youknowriad
approved these changes
Apr 14, 2020
youknowriad
reviewed
Apr 14, 2020
Co-Authored-By: Riad Benguella <benguella@gmail.com>
jorgefilipecosta
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When checking the bugs and understating if they are critical or not, knowing the version that introduces a bug is important. For example, a bug that was introduced three core WordPress versions ago and did not got any comments probably is not that "critical".
After the first major core WordPress beta version the first beta, we can only include bug fixes for issues that regressed during the "alpha phase" so knowing if a bug affects the last stable release of WordPress is essential. To triage issues.
Currently, our template just asks for the Gutenberg version. Most people just say WordPress 5.x, which is vague because without knowing if they have Gutenberg plugin or not, we can not conclude what versions of WordPress are affected. To improve this situation, I submitted a PR changing the template to ask:
With this information, we can make better conclusions about what versions are affected with less effort.
If users provide this information it will be much easier to make the triage. For example, when someone reports something without Gutenberg on WordPress 5.3.2, if we are after the core beta period, without further tests, it is already possible to conclude that at the stage we are, we will not be able to fix the issue.