I remember reading of Babel maintainers releasing betas and asking for feedback but not many helped; most just came to complain after the release.
Webpack 4 has been in beta for a while but not enough people tested it on real projects, evidently.
Webpack 4 has been in beta for a while but not enough people tested it on real projects, evidently.
[1] https://medium.com/webpack/webpack-4-beta-try-it-today-6b1d2...
[2] https://medium.com/webpack/webpack-4-released-today-6cdb9947...
Perhaps the naming is sending the wrong message? "Beta" sounds incomplete and subject to change; I certainly don't make a habit of introducing betas to serious projects unless there's something in them I'm desperate for.
An extended period of Release Candidate versions could give end users more confidence in adoption. This naming implies that the product is finalised and will be released as-is barring serious bugs. It's a small thing, but maybe giving end users the feeling of being early adopters rather than beta testers could increase uptake in this final critical stage.
https://reactjs.org/blog/2016/02/19/new-versioning-scheme.ht... (skip to the major versions and avoiding cliffs part)