All reasonable changes that should improve the QA process using BZ, especially the "last confirmed on" 4.0.0--just will need to be kept up going forward.
My +1 ps.s thanks for asking this time ;-) p.p.s a special CC for you Rainer so you are aware, here is the thread link in Nabble http://openoffice.2283327.n4.nabble.com/Updating-BZ-versions-for-next-releases-tp4649357.html ________________________________________ From: Rob Weir [[email protected]] Sent: Monday, August 05, 2013 10:38 AM ... I'd like to clean this up a little, as follows: 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. 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. 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. 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. 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. I'd love to hear your thoughts on this, even if it is just a quick +1. I'll hold off making any of these changes until this time Thursday. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
