[sldev] Results from Friday bug triage - next one planned for Monday, 3pm

[josh at lindenlab.com]

I did a quick scan over the bugs, and without reading this thread twice I
wasn't sure how to glean from the state in Jira what the triage call on a
bug was, or whether a bug had been triaged.

Even if the triage call is implicitly captured (e.g. by it being resolved
or by being linked to LL internal Jira), I think it's worth being
explicit, especially as it's nice to be able to focus on bugs that have
not yet been triaged (or were triaged and changed state).

Suggestions:

* Ensure the comments include a tag such as [SLDEV TRIAGE 2007-04-14], to
distinguish a group's triage call vs. "Who is Gigs Taggart and why do I
care what he thinks?"

* Add a new field in Jira, e.g. checkbox for "Triaged", text box for above
(triage by/date).

* Another possibility is to do the triage as a special "Triage" user, so
that comments by that user are known to be done by a team, and are
therefore searchable.

(The latter option has logistical/scaling issues.)



> Rob Lanphier wrote:
>> Please let us know what you think.
>
> I think we should reserve the meeting for the more controversial bugs
> that need discussion, and preemptively resolve the other ones.
>
> VWR-199 Solid repro, import
> VWR-203 Looks like the normal alpha sorting bug
> MISC-40 Doesn't make any sense to me.  Asked prok for clarification.
> SVC-45 Needs Repro
> VWR-208 Jeska reports it as known issue, might already have SL-id
> VWR-211 Account specific problem
>
> After doing this list I think it would be helpful if we could have more
> bug statuses/resolutions.
>
> 1. Needs repro - An invitation for someone to post a repro
>
> 2. Need more information (possibly this tag should be resolution, not a
> status)
>
> 3. Ready for Import (and/or linking with existing linden issue) -- This
> would mean it has a solid repro and/or someone has a patch attached.
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>