Hi,
During Chandler Engineering meeting yesterday afternoon
(http://wiki.osafoundation.org/Journal/EngineeringMeetingNotes20070118),
we thought that it would be good if we could identify the set of tasks
and bugs needed to be fixed in order to get Chandler 0.7alpha5 to a
"dogfoodable" state.
Dgfoodable means stable enough that it can be used by dogfooders, i.e.
that there's no data loss and no bugs that dogfooders can't cope with.
This is different from the Preview state where it's not only dogfoodable
but usable, i.e., there's no bugs with workaround or half-there
functionalities (things that dogfooders can live with).
For this, I created a new flag in Bugzilla simply named: dogfoodable.
PPD and QA will use it to flag all the bugs that are really required to
get to that stage. Everyone though is welcome to use it if you see a bug
you think that, as a user, you can't cope with.
Note that bugs flagged that way are not "blockers" or "higher priority"
than others, it's just a way to evaluate how far we are from this
dogfoodable state. So devs, though you're welcome to take a special look
at those, there's no immediate urgency for you to act when you see a
Bugzilla message saying that one of your bug has been flagged.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
