Blockers not being ranked as High is purely due to how we rank bugs. We can have something completely broken to a user, such as https://bugs.launchpad.net/inkscape/+bug/772057 which is Low. However, we should really avoid releasing with it at all costs. Would I let it completely block the release? Probably not... but it's one of those things that are so easy to hit, we should try to avoid releasing with it.
That said, 772057 may be temporarily fixed (at least for 0.91) when https://bugs.launchpad.net/inkscape/+bug/1387864 is fixed. Two blockers with one fix, are we that lucky?
Cheers, Josh
On Thu, Oct 30, 2014 at 1:32 PM, Bryce Harrington <bryce@...961...> wrote:
On Thu, Oct 30, 2014 at 01:21:54PM -0700, Josh Andler wrote:
On Thu, Oct 30, 2014 at 11:49 AM, Bryce Harrington <bryce@...961...> wrote:
Most of the remaining todo's on our roadmap are actually not that hard, and not that many, so I think a December release is not unrealistic.
I also want to remind people of the handful of blocker bugs still out there. https://bugs.launchpad.net/inkscape/+bugs?field.tag=blocker
I believe once we get the Windows libs straightened out we can remove the blocker tag from the cairo bug, if not otherwise marking it as not our issue.
Thanks, I was wondering if we had assembled a blocker list yet.
I'd wonder though if any bug ranked less than High importance is really a blocker...?
We should also ensure that all accepted blocker bugs have active assignees. We should probably also check that each of the blockers is getting a status update posted at least weekly.
Bryce