Question #1156
closed
Add another Tracker for Dev
Description
As discussed, maybe it is useful to add a new bug tracker for the dev team. So we can track the bugs in the dev version without compromising the bug statistic for the production version ;)
Updated by Alexander Watzinger about 4 years ago
- Tracker changed from Administration to Question
- Status changed from New to Closed
I thought about it and decided otherwise ;)
I know that I brought it up myself but I came to the conclusion that workflow is more important than cosmetic. We shouldn't be bothered with deciding which class of bug it is and the line can get fuzzy, e.g. in the Bootstrap feature we already identified 2 (very minor) bugs that were also in the production version but nobody noticed it before.
Dealing with bugs will always have the same priority: the highest. So if it's in productive it has to be resolved with the next version, if it's in a new feature it blocks the release of the feature.
About the statistic: OpenAtlas is actively developed and with one release about a month we are moving very fast. Even if the bug count should surpass the feature count we can take this as a sign of a very active and responsive development with many persons involved. The most important statistic is the open bug count and that we will keep to minimum anyway.
Of course in case anybody has a different opinion feel free to set it on the agenda of the next meeting to discuss it there.
Many thanks for following up, closing this issue.