As part of my RT 'clean-up' project I've been trying to get bug metadata
into a consistent state. Maybe someday we'll be able to generate some
worthless statistics that will look pretty in a presentation. :)
Anyways, It would be great if everyone handled bugs in the same manner.
I'm planning on writing a 'Bug Wrangling' document to outline some
suggested practices but I'm short on tuits this month. Since [PATCH]
bugs appear to be most frequently resolved bug type, here's a simple
checklist for how I'd suggest resolving them if the patch has been
applied.
- add correspondence to the bug stating that the patch was applied AND
the svn revision number.
- make sure that the bugs 'Tag' includes 'Patch'
- set the bugs 'Patch Status' to 'Applied'
- set the bugs 'Status' to 'resolved'
Cheers,
-J
--
- add the patch author to CREDITS or update the authors entry in CREDITS
- add correspondence to the bug stating that the patch was applied AND
the svn revision number.
- make sure that the bugs 'Tag' includes 'Patch'
- set the bugs 'Patch Status' to 'Applied'
- set the bugs 'Status' to 'resolved'
-J
--
>It looks like the CREDITS file hasn't been getting updated. I'd like
>to revise that check-list to:
>
>- add the patch author to CREDITS or update the authors entry in CREDITS
>- add correspondence to the bug stating that the patch was applied AND
> the svn revision number.
>- make sure that the bugs 'Tag' includes 'Patch'
>
>
I've got three more:
- Claim ownership or interest ( CC ) of the ticket. In this way you will
be received further correspondence about the ticket.
- Run the test suite
- make manitest
>- set the bugs 'Patch Status' to 'Applied'
>- set the bugs 'Status' to 'resolved'
>
>
CU, Bernhard
> Hi Folks,
>
> As part of my RT 'clean-up' project I've been trying to get bug
> metadata
> into a consistent state. Maybe someday we'll be able to generate some
> worthless statistics that will look pretty in a presentation. :)
I appreciate this ver much, but ...
> - add correspondence to the bug stating that the patch was applied AND
> the svn revision number.
> - make sure that the bugs 'Tag' includes 'Patch'
> - set the bugs 'Patch Status' to 'Applied'
> - set the bugs 'Status' to 'resolved'
... this list looks for sure like stuff a computer can do. We have svn
(which can run action scripts), RT (which is scriptable afaik). I think
it should be possible to properly close PATCHes automatically.
> Cheers,
>
> -J
leo