Rob Weir schrieb:
Hi Rob,
1) It is reasonable for someone to report a bug using 3.4.0, 3.4.1 or
4.0.0. None of these versions are "end of life" so they should be
allowed for new bug reports.
I agree.
An additional hint: for me the Version is an important distinguishing
mark. Of course the exact version of appearance can be mentioned in a
comment, but that is not very clear and can not be used for reliable
queries. So for me selectable versions like 3.3.x or similar to narrow
down version of appearance would have some benefit, and may be also for
developers it might be useful to have easy access to reliable version
info, what might ease to find the code and commit causing the problem.
But of course, such versions only are useful if many users use them that
way.
2) I don't see the purpose of "AOO PleaseHelp" as a milestone version.
Are we overloading meaning in this field? If we really need track
issues that need help we should define a keyword for this. So I'm
inclined to delete this milestone version number.
+1
3) I'd also like to simplify the versions across the board to be just
"3.4.1", "4.0.0", etc., without the "AOO" prefix.
+1
Discharging that ballast also eases use of regular expressions in queries
4) For Last Confirmation On, I'd like to hide values except for 4.0.
We should not be confirming bugs without testing on the most recent
version. Sure, new bugs can set "Version" to 3.4.0 or 3.4.1, but
confirmation should occur on 4.0.
+1
If someone can confirm a bug with 3.4.1, but no longer with 4.0, he
should close that bug, or ask for help, but I can't see any benefit for
a new entry "Last confirmed with 3.4." or so.
5) I'll add a new Target Milestone of "4.0.1" and Version of
"4.0.1-dev" since it is likely that we will have a 4.0.1 release to
address some of the defects that have been reported on 4.0.0.
Sounds plausible.
Best Regards
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
