Can you add a release schedule to the readme? #457
Labels
Comments
codeboten
pushed a commit
that referenced
this issue
Jan 26, 2022
Update the release section of the readme to include the monthly cadence of releases. Fixes #457
codeboten
pushed a commit
to codeboten/opentelemetry-python-contrib
that referenced
this issue
Jan 26, 2022
Update the release section of the readme to include the monthly cadence of releases. Fixes open-telemetry#457
Merged
ocelotl
pushed a commit
that referenced
this issue
Jan 26, 2022
* updating changelogs and version to 1.9.0-0.28b0 (#875) * Release Botocore Instrumentation as 0.28b0 (#878) * add note about monthly cadence Update the release section of the readme to include the monthly cadence of releases. Fixes #457 Co-authored-by: Owais Lone <owais@users.noreply.github.com> Co-authored-by: Nathaniel Ruiz Nowell <nathanielruiz98@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
When compared with the base
opentelemetryrepository, this one contains a lot of instrumentations and subpackages, and the rate at which bugs are fixed will keep being relatively bigger over time (more instrumentations, more bugs). After a fix for a specific instrumentation is out, there is no way to know when it will be in a release.Describe the solution you'd like
Define (or share) a schedule for releases. It does not have to be that often. The added clarity is valuable for people using the package.
Describe alternatives you've considered
Installing the instrumentation I need directly from github.
Additional context
This is mostly a documentation issue (if there is a release schedule in place already). If there is not a set schedule, we could define something.
The text was updated successfully, but these errors were encountered: