|
I wait a few days before deciding to download a new release to see if any reports of bugs shows up (assuming the release contains a new feature and/or bug fix I'm interested in). I'm watching 0.7.38 right now since it has a bug fix I requested. The only complaint I've seen so far was immediately fixed so it's looking good for me.
Keep in mind this program is still under development and I expect it will be for a long time (which is a good thing since it keeps getting better) so there will be occasional bugs slipping by so those who download new releases are essentially beta testers. Unlike commercial programs that do the same thing (the company that puts out my music notation program is especially notorious for this), fixes for reported bugs are rarely more than a week away instead of only once or twice a year (if that often). The only time I have had to revert to an earlier version because of a bug was with 0.7.35 and I didn't catch it right away (I was probably one of six people affected by it). Fortunately, I keep the previous half dozen or so installation files just in case.
If you don't want to be a "beta tester" for each update, just watch the boards for a few days after a release for any complaints about bugs before updating. Also check the change logs before updating. If there are no fixes or changes of interest to you, there is no point in updating. I usually skip a few updates just for that reason and I don't feel I'm missing out on anything.
|