On Wed, Dec 5, 2012 at 2:55 AM, Tavmjong Bah <tavmjong@...8...> wrote:
We need the input of Krzysztof here. I've looked at some of the bugs. They require a good knowledge of how the rendering code works. I've managed to fix one but a fix for another of the bugs has introduced regressions elsewhere. Our choices are:
- Go ahead with the release with the current rending bugs.
- Delay the release until the bugs are fixed.
We can do alpha, beta, or pre-releases with the current rendering bugs, but I am uncomfortable doing a stable release with them. If a majority vote were to be to release with them, I would have to step aside as release warden this cycle as it would be an issue for me.
If we chose (1) then we should be in feature freeze. If we chose (2) then we can have a feature thaw (using a staging branch).
Seems sensible.
I thought we had a solution for the security bug.
Johan & I emailed about this earlier. So, I'm waiting to hear back or see a commit.
I am a bit worried about branching too early. I have found that working in branches can quickly lead to code rot. I had to spend several days getting my Mesh branch to work with trunk after not touching it for a couple of months (which is why it got checked in even though disabled by default).
I do share your worry. Any thoughts on the scripting to avoid it suggesting from my other message?
Cheers, Josh