From The Linux Foundation
Contents |
Open Issues
Vision
In previous LSB project management schemes, everything has been tracked through Bugzilla. For the LSB 4.0 project, we will be doing much more via the Project Wiki pages. Essentially, if a issue is "big enough" that requires multiple people or has multiple (non-trivial) subtasks to complete, it should be tracked as a project, not as a bugzilla entry.
So what we need to do is to go through all of the open bugs, and decide which ones should be an open project, and create a wiki project page. For bugs that remain as BZ entries, they need to be prioritized via a P1/P2/P3/P4 scheme.
Milestones
| Milestone | Plan Date | Outlook | Comments |
|---|---|---|---|
| E-mail ballot sent | March 10 | ||
| E-mail ballot returned | March 17 | ||
| Bugzilla mass prioritization finished | March 28th |
A rough proposed schedule for this project. When we anticipate that we will reach certain milestones. Also, if the project has an absolutely-must-be-completed-by date, mention it here.
Resources
What resources have been dedicated to this project?
Contacts
| Name | Role |
|---|---|
| Theodore Ts'o | Project Owner |
Tasks
Tasks will map many-to-one to milestones. Tasks are specific actionable work items that need to be completed in order to reach a milestone
Active
| Task | Owner | Status | Outlook |
|---|---|---|---|
| Create text list of open LSB 4.0 bugs | tytso |
Completed
Comments
A note on Bugzilla priorities
P1 means that it is a release blocker; if it is not done, LSB 4.0 can not ship. P2 bugs are highly desirable to ship. P3 and P4 are different variants of nice to have, and will be done if we have spare time. P5 basically "we'd close this because it is so highly unlikely we'll ever have the time to fix this, but it really is technically a flaw and so we're embarrassed to close it, or there are political reasons why we can't close it." In my experience, it's extremely rare that a process has enough resources that P4/P5 bugs get addressed, although in some cases they might be good things for new members of the LSB workgroup or students interested in getting involved to work on.Theodore Tso 08:33, 5 March 2008 (PST)