| 1 |
On czw, 2017-03-30 at 14:41 -0400, William L. Thomson Jr. wrote: |
| 2 |
> On Thursday, March 30, 2017 2:34:56 PM EDT Kent Fredric wrote: |
| 3 |
> > |
| 4 |
> > _Especially_ when a developer marks a ticket as that without adequate |
| 5 |
> > explanation as to why. |
| 6 |
> |
| 7 |
> That sounds like the problem. Do not rely on status/keywords alone. Anytime |
| 8 |
> those change, a comment should be included as to why. That seems like it would |
| 9 |
> clear up much of the confusion. Simply do not change status/keywords without a |
| 10 |
> comment to briefly explain the change and/or usage. |
| 11 |
> |
| 12 |
|
| 13 |
Because obviously everyone has lots of time to open multiple bugs just |
| 14 |
to find where the developer should have explained what he meant when he |
| 15 |
closed the bug using unclear status. |
| 16 |
|
| 17 |
While at it, maybe we should just remove all resolutions and expect |
| 18 |
people to open every bug and read comments. Or maybe remove statuses |
| 19 |
altogether, that will clear every confusion possible! |
| 20 |
|
| 21 |
-- |
| 22 |
Best regards, |
| 23 |
Michał Górny |
Archives