Hi,
We've been triaging m5 bugs this afternoon and, as promised earlier,
here's our current status:
- We have 18 bugs open on m5: ideally, all these bugs need to be checked
in before Tuesday night though, obviously, some bugs have a higher
priority than others and non-critical or blocker bugs might be punted
(especially if the fix is too risky...).
- 7 of those 18 bugs are marked blockers: those are bugs (mostly
regressions) that we need to fix in order to declare m5. We will hold on
m5 as long as those bugs are not fixed so those are definitely the
highest priority.
- John has 3 bugs assigned and all 3 are blockers: this is partially
because Ted is going in vacation and John is the one who knows this code
best (after Ted). Since it's a little too much for any one single person
to hold so many blockers, John will do an assessment of the issues and
may ask devs with no critical bugs to help out. So, even if you have no
blocker assigned to you, you're still on active duty on m5... :)
- Keep an eye on incoming bugs: we're still testing and logging bugs,
they are triaged daily so things can still show up on your list.
- For the bugs we moved to m6: you can still commit fixes for those bugs
till Monday night. Use common sense and refrain of commiting anything
you know is risky or likely destabilizing. Starting Tuesday, we'll start
imposing code review for all commit and limit them to m5 bugs only (see
Bear's e-mail).
Looks like we're narrowing down on a very good milestone here with
impressive new features and architectural work. We've plenty of work for
m6 for sure but we're pretty confident 0.6 will look very very nice.
Thanks to all and keep up the great work!
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
