Smaller and more frequent releases

[sheepsteak]

The milestones set on the project are quite large and this has a few knock on effects such as:

• more risk for each release - all these issues for a 4.0.1 ➡️ 4.0.2 patch release
• lots of noise and questions asking when merged PRs will get released
• duplicate issues for things already fixed but waiting to be released

For example, this small PR I did to fix the TypeScript peerDependency issue has been merged for a few months and is helpful to fix how npm7 now works with peer dependencies. However, it's caught up in the 4.0.2 milestone that has another 15 issues waiting to be fixed.

Is it possible to start making smaller releases so we can get some of this stuff released? I can see you're very busy and probably have limited time to work on and maintain the project so do we need more maintainers to help with this?

[arogozine]

I think a monthly cutoff and release would be ideal. It would allow us to plan for fixes and changes effectively.

[sheepsteak]

We have a 4.0.2 release! 🎉

Thanks, CRA team!