On Mon, Dec 02, 2013 at 04:24:41PM -0800, Josh Andler wrote:
To expand a little further though, we have been piling up regressions from previous releases too... as su_v mentioned, that list is what is milestoned for 0.49 and tagged with regression. If you remove the milestone the list is actually twice as many.
I think we might want to target at least a few of these to 0.49, such as https://bugs.launchpad.net/inkscape/+bug/484507
I'll go over the list of them over the next few days to see what (if anything) should be tagged with blocker. I'm also of the mindset of su_v about what we ought to try for with that milestoned regression list.
Sounds good. I'd like to organize bug hunts again like we've done in the past; I know they're silly but they've been effective at motivating devs to fix scads of bugs in short order.
If you get together a list of blockers, I'd like to actually do two bug hunts.
The first would be an elite bug hunt that targets only bugs on the blocker list (or the milestoned regression bugs on suv's list). The goal not being to close all the regressions, but to clear a large enough chunk that we feel more confident about being ready for release.
Then a second open season bug hunt, for any and all bugs filed against Inkscape. We could set a pretty high target here. The goal here is just general cleanup and encouraging developers to shift focus to bug fixing.
After that, we'd fork a stable release branch and focus on whatever blockers remain.
There'd also be the usual chill/frost/freeze stages mixed in with the above.
If we could have 0.49 with less regressions than it started with, it would be a nice bonus for everyone and a great achievement.
Agreed. At the same time hopefully we don't have a few hard blocker bugs delay the release indefinitely. At some point the cost-benefit of getting those last few issues ironed out will fall below the value of getting all the other assorted fixes and features out to users.
Bryce