main doc: flutter.dev/go/package-release-strategy

There are several rules to follow when maintaining a package with batch release. This doc ideally should be a guide somewhere in our readme or style guide

It should have the following

1. Why should one uses batch release
2. How would one opts in or out of the batch release (including ci configuration)
3. How to guide contributor to contribute to the package after opts in

• Regular contribution
• no changelog/version bump needed
• Reverts

4. How release works (both periodically or manually)

5. FAQs

• How to handle releases when all ci failed
• Retracting bad release
• Where to track a release goes out correctly.
• grouping breaking changes