Currently, the "Version" field of our bugs can only be set to one of "compat (1.0)", "core (2.0)" or "unspecified". Why not to create a new "both" option to explicitly indicate that the bug is valid for both versions? So, "unspecified" would only mean that the bug has not been tested on both versions. (Ideally, the "version" field should consist of two checkboxes, one for each version.)
Agree
Another thing is some bugs are for specially python versions (in all of them it's mentioned) but we don't have anything to categorize them but we have really redundant options like "web browser", "mobile platform". I don't know is it possible to change or remove these parts?
Best
On 7/27/14, Ricordisamoa ricordisamoa@openmailbox.org wrote:
Currently, the "Version" field of our bugs can only be set to one of "compat (1.0)", "core (2.0)" or "unspecified". Why not to create a new "both" option to explicitly indicate that the bug is valid for both versions? So, "unspecified" would only mean that the bug has not been tested on both versions. (Ideally, the "version" field should consist of two checkboxes, one for each version.)
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
I disagree with adding 'both'.
I think we should use the whiteboard, or a tracking bug, for core bugs inherited from compat and the fixes therefore need backporting.
On Sun, Jul 27, 2014 at 7:35 AM, Ricordisamoa ricordisamoa@openmailbox.org wrote:
Currently, the "Version" field of our bugs can only be set to one of "compat (1.0)", "core (2.0)" or "unspecified". Why not to create a new "both" option to explicitly indicate that the bug is valid for both versions? So, "unspecified" would only mean that the bug has not been tested on both versions. (Ideally, the "version" field should consist of two checkboxes, one for each version.)
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l