destiny team mailing list archive

[Zach Elko <zachelko@xxxxxxxxx>]

Just another note here:

Once a bug has the "Fix Committed" status, and the fix has been verified via
comments on the bug by users of both Linux / Windows, the status should be
changed to "Fix Released". This will cause the bug to stop appearing in the
list. Chances are, I'll personally handle this responsibility, but just a
heads up about how the process works.

Zach J. Elko
Ball State University Unified Technology Support
Certified Hardware & Software Technician


On Sat, Feb 6, 2010 at 7:29 PM, Zach Elko <zachelko@xxxxxxxxx> wrote:

> Some guidelines and notes about the bug tracker:
>
>
>    - I expect everyone to keep an active eye on the bug listing within
>    Launchpad (not just the e-mails)
>    - When a bug is reported, it should remain in the "New" status until
>    someone else can replicate it using the steps listed in the bug's
>    description. When someone does that, they should change the status to
>    "Confirmed". This ensures that we aren't reporting bugs that only exist on
>    one person's machine, and that the bug is actually a bug.
>    - If you see a bug you think you can fix, change the status to "In
>    Progress" before working on it. This lets everyone else know that someone is
>    working on it.
>    - If you fix a bug, add a comment to the bug stating which revision you
>    committed the fix in, and then change the status to "Fix committed."
>    - If you see a bug is in the "Fix committed" status, you should update
>    your repository and try to replicate the bug. If you can't, great. Add a
>    comment to the bug and state that you can confirm the bug has been fixed.
>
> Zach J. Elko
> Ball State University Unified Technology Support
> Certified Hardware & Software Technician
>