Here is our current stats. Overall situation looks ok. We have manageable
number of high priority bugs. Number of medium bugs is going down. It
doesn't look like we will fix all medium bugs by end of release but it
seems to be acceptable. High priority technical debt is under control.
Features back
Hi guys,
new report is based on 'area' tags. I'm sorry for hardly readable heap of
numbers. Here are values for current numbers of open bugs, number of bugs
opened since last Thursday and number of closed bug for the same period.
Bugs in python, library and UI areas. Format: Total open(UI open/Py
Guys,
1) Bugs status
Here is our current stats. Again I’ll show it in format “total (UI / python
/ library)"
Critical and high bugs: 52 (6/28/18). Last week it was 46 (1/23/22)
Medium, low and wishlist bugs: 196 (41/112/43). Last week it was 193
(47/104/42)
Features tracked as bug reports: 143.
Dmitry,
2015-10-22 21:42 GMT+07:00 Dmitry Pyzhov :
> Guys,
>
> 1) Bugs status
>
> Here is our current stats. Again I’ll show it in format “total (UI /
> python / library)"
>
> Critical and high bugs: 52 (6/28/18). Last week it was 46 (1/23/22)
> Medium, low and wishlist bugs: 196 (41/112/43). Las
Vitaly,
because first goal is to make clear separation for bugs ownership.
'area-python' means 'this bug is tracked in python team statistics and it's
python leads job to push it forward'. You can use any other tags you want
to track ui-related bugs. Just don't use 'area-' prefix for that.
I've c
