Thomas Dinges has published a good overview of what YOU can do to help improve the quality of Blender releases.
We just released Blender 2.67b , the second bugfix release for the Blender 2.67 version. In a 2 month release cycle this is not really nice, and we all would like a stable Blender release. I don’t blame anyone, errors happen and they can happen everywhere. But I think that together, we can do better. So the question is how we can avoid those “a” and “b” update releases.
We always release an release candidate, about 1 week before the real release happens, which gives everyone time to test the new version.
Here are 3 questions you should ask yourselves:
- Do you download the release candidate (RC)?
- Do you test the RC with your everyday blend files, to see if the things you usually do, still work?
- If you find a bug, do you report it to the bug tracker, so we know about it?
If you can answer all those 3 questions with yes, it’s great and I want to thank you for that. If the answer is no though, I hope that you will reconsider! Please keep reading.