On Tue, 2009-11-03 at 16:25 -0500, bulia byak wrote:
Is this patch being worked on? It's been my impression that the issue is at least hard to reproduce, to start with.
Jon, care to comment?
I may be wildly off the mark, but I would vote to release right now.
I will be honest that even if it is an issue, if we don't have a fix in sight, it's worth releasing with this so we all can get on with active, collaborative development.
How do we define "major"?
Well, typically something that we would label as a refactoring task. However, if someone has a "major" change and throws it in a branch and it is deemed to be safe enough to be worth the possible risk for 0.48, we'll merge it.
Generally I'm in favor of making 0.48 more restrictive, because otherwise we won't be able to do it fast. I'd suggest that people start working on patches already, so they are ready to commit when we reopen!
I completely agree!
Such policy is an absolute must, and mostly we adhere to it. I think it only gets violated when the damage is discovered too late when the original author is no longer available.
Well, this possibly ties into the branches stuff. I've noticed a few times where people commit stuff and then leave on vacation or the like. So, if someone has a number of changes that they want to commit and know they will be unavailable for a few weeks to a few months or longer, put it in a branch. Honestly, the same goes for "Here's what I've done, I don't feel like working on it anymore" type contributions, until they've been deemed safe to merge.
Cheers, Josh