Issue Tracker

Everything about development and the OpenMW source code.
User avatar
Site Admin
Posts: 1193
Joined: 05 Aug 2011, 22:21
Location: Wroclaw, Poland

Issue Tracker

Post by lgromanowski » 15 Aug 2011, 09:36

Zini wrote: Edit: As the first component our tracker has been migrated to the new site:

Please register there. The old tracker is officially closed now.

Edited ...

We now have an issue tracker:

Currently you need a separate account on Mantis. The forum account won't work.

For now we will use Mantis to track bugs and as a replacement for our previous roadmap page.

What goes not into the tracker:

- feature requests (we have a wiki page and a forum for them)

What goes into the tracker:

- unimplemented features, that are part of Morrowind
- bugs in already implemented features, that are caused by an oversight or a mistake during the implementation
- all kind of regressions

I suggest we use the following guidelines for the various fields in the bug report:

Taken from the mantis manual:
* New - This is the landing status for new issues. Issues stay in this status until they are assigned, acknowledged, confirmed or resolved. The next status can be "acknowledged", "confirmed", "assigned" or "resolved".

* Acknowledged - This status is used by the development team to reflect their agreement to the suggested feature request. Or to agree with what the reporter is suggesting in an issue report, although they didn't yet attempt to reproduce what the reporter is referring to. The next status is typically "assigned" or "confirmed".

* Confirmed - This status is typically used by the development team to mention that they agree with what the reporter is suggesting in the issue and that they have confirmed and reproduced the issue. The next status is typically "assigned".

* Assigned - This status is used to reflect that the issue has been assigned to one of the team members and that such team member is actively working on the issue. The next status is typically "resolved".

* Resolved - This status is used to reflect that the issue has been resolved. An issue can be resolved with one of many resolutions (customizable). For example, an issue can be resolved as "fixed", "duplicate", "won't fix", "no change required", etc. The next statuses are typically "closed" or in case of the issue being re-opened, then it would be "feedback".

* Closed - This status reflects that the issue is completely closed and no further actions are required on it. It also typically hides the issue from the View Issues page. Some teams use "closed" to reflect sign-off by the reporter and others use it to reflect the fact that the fix has been released to customers.
For the Severity field I suggest the following:

* trivial: A papercut-class problem
* minor: A minor annoyance, that can be worked around
* major: A major annoyance, that limits the usefulness/testing-scope of OpenMW
* crash: That should be obvious
* block: Can't release, until this is resolved.
Zini wrote: I know I just wrote, that we should not use the tracker as a replacement for the roadmap. But after playing around with it a bit, I have come to the conclusion, that it would be beneficial to merge both.

Does anyone have objections against integrating the roadmap into the tracker? This would require every developer to sign up on the tracker separately.
Zini wrote: Since nobody yelled "stop" and nobody tried to ridicule me about being so inconsistent about this topic, I assume nobody has objections.

I will start to dump the roadmap onto the tracker. All developers, please register at our tracker (re-use your forum name).
pvdk wrote: Ah forgot to reply, I think it's a good idea, will register.
Zini wrote: Started to transfer the roadmap, but it looks like this will take a while. Not sure if I can finish today.
Zini wrote: The new roadmap for 0.11.0 is up: ... ?filter=52

Entering the other tasks for future milestones will take a bit longer.
Zini wrote: Done. 115 issues in the tracker. We probably will get some more bug report issues. And some issues may need to be split in two or more. But in general, once we have these 115 issues handled, we will have a fully working Morrowind implementation.

btw. we still need developers to sign up on the tracker. So far I only see gus and peppe.
Zini wrote: I see a user with the name of Prevedpalad on the tracker. Who is that?
pvdk wrote: I registered as pvdk.

Looks good Zini.
Zini wrote: Thanks! Still waiting for 3 developers to sign up.
corristo wrote: I'm here
jhooks1 wrote: I registered.
gus wrote: Can we see suggested task on the issue tracker?
Zini wrote: This category is gone. It has been merged into the regular 0.11.0 roadmap.
Zini wrote: Plugged a few holes in our issue list (5 new issues).

Edit: make that 6. *sigh*
Star-Demon wrote: I'm registered up. :)
Zini wrote: Important note: If someone needs to change an issue's status to resolved, please adjust the field "Fixed in Version" accordingly. This will make Mantis generate a nice change log for us automatically:
Zini wrote: The old tracker is closed now. Please use the new one (see first posting).
best regards,