Thanks for thinking about this issue, Kathey. I agree that it would be
good to triage bugs created after the 10.5.2 effort. The highest bug
touched by that effort seems to be DERBY-4295. What is the motivation
behind re-triaging the bugs visited during the 10.5.2 effort? Have we
added new checkboxes or tags which need to be applied uniformly across
the bug database? If so, then it would be helpful to highlight those new
checkboxes and tags so that people will know what to focus on during a
re-triage. Did we make a lot of mistakes during the 10.5.2 triage effort?
Thanks,
-Rick
On 2/9/11 6:17 PM, Kathey Marsden wrote:
On 2/9/2011 4:49 PM, Kathey Marsden wrote:
I was looking at Dag's triage page for 10.5.2 [1] and would like to
set up something similar for 10.8.
Correction the in construction 10.8 page is:
http://wiki.apache.org/db-derby/DerbyTenEightOneBugTriage
Dag's 10.5.2 page for comparison is:
http://wiki.apache.org/db-derby/DerbyTenFiveTwoBugTriage
I think that it would be nice to add the use a "derby_triage10_8"
label in addition to marking the urgency field.
so that we can 1) See how recently issues have been triaged 2)
Invite more casual triage. The links on the 10_8 page would just be
links to blocks of untriaged issues by component rather than specific
issues and would reduce as issues are triaged. I got started on the
page, but obviously have not yet put in all the links which I will
try to do later this week. Please let me know if you have any
feedback or think a different format would be better.
http://wiki.apache.org/db-derby/DerbyTenFiveTwoBugTriage
Thanks
Kathey
