opentelemetry-js icon indicating copy to clipboard operation
opentelemetry-js copied to clipboard

Published 20 hours ago • verified publisher icon open-telemetry

Formalize API release cadence

Open dyladan opened this issue 3 years ago • 9 comments
trafficstars

We are currently preparing for the 1.1 release, but for features which did not make it into the release I believe we should have a more formal answer for when they may be expected to be released. I don't think we need anything very complicated or process-heavy, but I would suggest something like this:

  • 1 minor release per month if there are new features ready
  • 2 weeks before release, maintainers will look at open issues/PRs and determine which should be included in this month's release. Issues that are to be included will be added to the release milestone.
  • Any features not added to the current release milestone should be added to the next release milestone by default unless an argument can be made to bring them forward or push them back.

dyladan avatar Jan 20 '22 13:01 dyladan