If you have to do a bug fix release very shortly after a feature release,
doesn't this hint that the feature release was really not much tested?
I guess it depends on your opinion of what amount of testing should be done before each new release, and how much of the developers time and effort you want spent on managing a large group of beta-testers, instead of spending that time on more future development.
I like the current model that the MorphOS Development Team uses, where a relatively small group of talented developers creates the new features, tests them on as many different hardware choices they have available to them, then releases a new version of MorphOS to the public. As others have said, each major release is usually followed shortly by a "bug-fix" release a few months later, as the team gets feedback from the MorphOS community.
It is a pattern that has worked out quite well and I believe that most MorphOS users are very happy with the results and the frequency of new releases of MorphOS. I know that I am extremely happy with the decisions that the MorphOS Development Team have made and the direction they have taken for the past several years. IMO, their choices always seem to make the best common sense.
