From Fedora Project Wiki
< BugZappers | Meetings
(New page: = Agenda for 2008-Jul-29 = == Logistics == * Date: Tuesday, July 29, 2008 * Time: 17:00UTC * Location: #fedora-meeting on [http://freenode.net freenode] == Current status == ______ ...) |
No edit summary |
||
| Line 20: | Line 20: | ||
{| border="1" | {| border="1" | ||
|- | |- | ||
||Status / Version||8||9 | ||Status / Version||8||9 | ||
|- | |- | ||
||ASSIGNED||888||1471 | ||ASSIGNED||888||1471 | ||
|- | |- | ||
||MODIFIED||120||224 | ||MODIFIED||120||224 | ||
|- | |- | ||
||NEEDINFO||264||231 | ||NEEDINFO||264||231 | ||
|- | |- | ||
||NEW||1737||2519 | ||NEW||1737||2519 | ||
|- | |- | ||
||ON_DEV||2||4 | ||ON_DEV||2||4 | ||
|- | |- | ||
||ON_QA||55||87 | ||ON_QA||55||87 | ||
|- | |- | ||
||POST||10||22 | ||POST||10||22 | ||
|- | |- | ||
||RELEASE_PENDING||1||0 | ||RELEASE_PENDING||1||0 | ||
|} | |} | ||
| Line 43: | Line 43: | ||
{| border="1" | {| border="1" | ||
|- | |- | ||
||Status||Number of bugs | ||Status||Number of bugs | ||
|- | |- | ||
||ASSIGNED||354 | ||ASSIGNED||354 | ||
|- | |- | ||
||MODIFIED||33 | ||MODIFIED||33 | ||
|- | |- | ||
||NEEDINFO||48 | ||NEEDINFO||48 | ||
|- | |- | ||
||NEW||905 | ||NEW||905 | ||
|- | |- | ||
||ON_DEV||1 | ||ON_DEV||1 | ||
|- | |- | ||
||ON_QA||17 | ||ON_QA||17 | ||
|} | |} | ||
Latest revision as of 23:01, 26 July 2008
Agenda for 2008-Jul-29
Logistics
- Date: Tuesday, July 29, 2008
- Time: 17:00UTC
- Location: #fedora-meeting on freenode
Current status
______ currently open Fedora bugs!
F8 and F9
| Status / Version | 8 | 9 |
| ASSIGNED | 888 | 1471 |
| MODIFIED | 120 | 224 |
| NEEDINFO | 264 | 231 |
| NEW | 1737 | 2519 |
| ON_DEV | 2 | 4 |
| ON_QA | 55 | 87 |
| POST | 10 | 22 |
| RELEASE_PENDING | 1 | 0 |
Rawhide
| Status | Number of bugs |
| ASSIGNED | 354 |
| MODIFIED | 33 |
| NEEDINFO | 48 |
| NEW | 905 |
| ON_DEV | 1 |
| ON_QA | 17 |
Special Topic
We will be addressing progress made on bugs of status NEW, as well as progress made on cleaning up the documentation. There is also some discussion on starting some type of Bug Hour, that would serve as a training, as well as a "social" bug triage time. And as before we will set goals for next week.