Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish release cadence for collector-contrib #1631

Closed
alolita opened this issue Nov 18, 2020 · 5 comments
Closed

Publish release cadence for collector-contrib #1631

alolita opened this issue Nov 18, 2020 · 5 comments
Labels
ci-cd CI, CD, testing, build issues enhancement New feature or request Stale

Comments

@alolita
Copy link
Member

alolita commented Nov 18, 2020

What is the release cadence for the collector-contrib binaries? We'd like to get the latest merged changes in a collector-contrib release.

Can you please publish the release cadence for collector-contrib and the Collector (e.g. every week, 2 weeks) for when to expect a new release? This helps us test with published artifacts instead of cherry-picking commits to build artifacts.

Can this release process be automated with a GHA workflow? We can help build this workflow.

@tigrannajaryan
Copy link
Member

Collector core and contrib are released biweekly (today is a release day). The release process is described here https://github.com/open-telemetry/opentelemetry-collector/blob/master/docs/release.md
Further automation of the process is very welcome.

@alolita
Copy link
Member Author

alolita commented Nov 30, 2020

Hi @tigrannajaryan Thanks for the link. I looked at release.md but it doesn't seem to state the release frequency for the Collector builds to be available. I'm working with @AzfaarQureshi and @shovnik on migrating the Collector release workflows from CircleCI to GitHub Actions. Feel free to ping me if there are other workflows you have in mind that we can automate for nightly and stable release builds. See related issue here.

@andrewhsu andrewhsu added enhancement New feature or request and removed feature request labels Jan 6, 2021
dyladan referenced this issue in dynatrace-oss-contrib/opentelemetry-collector-contrib Jan 29, 2021
* Remove ConsumerOld

Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>

* Fixed comments

Co-authored-by: James Bebbington <jbebbington@google.com>
@alolita alolita added the ci-cd CI, CD, testing, build issues label Sep 2, 2021
ljmsc referenced this issue in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
* sdk/trace: add missing options to tracer provider

This change adds `WithDefaultSampler` and `WithSpanLimits` to the tracer
provider and removed `WithConfig` from it.

Before this change, `WithConfig` is the only way to set sampler or
limits of a span. However, it is prone to misuse, since `WithConfig` can
override tracing configurations that are configured by `WithResource` or
`WithIDGenerator`.  Thus to fix this, it adds new functional options -
`WithDefaultSampler` and `WithSpanLimits` and removes `WithConfig`.

Resolves #1631.

* Update sdk/trace/provider.go

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>

* Update sdk/trace/provider.go

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>

* rebase and remove WithConfig

Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2022

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 4, 2022
@andrzej-stencel
Copy link
Member

I suppose this can be closed now, what do you think @evan-bradley? Given that the release.md file now includes the release schedule table at the bottom.

@evan-bradley
Copy link
Contributor

I would agree, closing this as completed. Thanks @astencel-sumo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd CI, CD, testing, build issues enhancement New feature or request Stale
Projects
None yet
Development

No branches or pull requests

5 participants