Honestly, we have tried this strategy in the past. The issue is that we end up spending an inordinate amount of time supporting the unstable versions despite any warnings we put in the docs or the software itself.
As a software developer, I'd love to get our code out there and tested by more people more quickly. But we can't do that at the risk of overwhelming our support organization. We're open to ideas of how to improve this, but simply putting warnings in the software and release notes has failed to tame the support burden of putting software with known issues into the field.