Stephen Hahn wrote:
* Richard Lowe <[EMAIL PROTECTED]> [2006-09-15 16:09]:
But it isn't just sponsorship. If I file a CR, I have to ask someone
within Sun to update it with additional information for me, ....
As opposed to some of the more energetic statements in this thread,
here's one we might be able to act on.
Modifications to existing bugs can certainly be implemented. (As a
disappointing, but practical, note, the submission form is not part of
the query application that has everyone upset. Therefore, we could
figure out how to add additional modification capabilities.) What's
less clear to me is who should be able to update a bug: the
contributor with assigned sponsor? some new special class of
contributors? any registered user?
The person who filed the CR, and anyone working on the CR certainly.
Though the latter is somewhat problematic, given that it's common to
request a sponsor when you're done, or almost done with a CR, and
that's the only real indication that it's being worked on.
And what fields should be
modifiable: just the description? fields that can't currently be
seen in b.o.o.?
At least the same fields that can be set while filing a CR. (excluding
any that are intended to be write-once)
It seems to have become fairly common (from out here), to use
Description as a hybrid Description/Evaluation, and Work Around as Work
Around and Suggested Fix, so in theory that practice could continue
without resorting to write-only fields, which seem like they would be a
clear path to further annoyance without some way to mark those fields
as externally originated (which gets back into the existing problems
rather quickly).
We can probably characterize this work well enough that it can be
worked on, if people are interested.
- Stephen
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
