Pablo Baeyens comments

Results 778 comments of


                                            Pablo Baeyens

[docs/component-stability.md] Add criteria for graduating between stability levels

I split off part of this PR in #11937. PTAL at that one first

Make the release process fully happen within GitHub Actions

@jackgopack4 Nice! Updated the list above

Make the release process fully happen within GitHub Actions

I feel like this could be removed from the Collector v1 project at this point. I am supportive of @mowies proposal above and I think it should be a priority...

[docs/component-stability.md] Add criteria for graduating between stability levels

@ArthurSens I think those concerns are reasonable, we definitely need more automation to be able to do this at scale and over time. I think the focus at this stage...

[docs/component-stability.md] Add criteria for graduating between stability levels

I intend to merge this in a couple of days if there are no further comments

[docs/component-stability.md] Add criteria for graduating between stability levels

> Are there any plans regarding "technical stability/maturity"? For instance, a threshold of test coverage and/or linting issues. @douglascamata Yes! see #11553 for the full list of things I want...

[docs/component-stability.md] Add criteria for graduating between stability levels

@djaglowski I will wait a bit more in case you have further comments and merge this on Monday morning

Release the operator v0.111.0

I think this is unblocked now, right?

Use Go 1.20 `errors.Join` instead of `go.uber.org/multierr`

I removed the `good first issue` and `easy` labels and added `on hold` instead. The 'easy' way to change the code to use `errors.Join` means creating a slice of errors,...

Use Go 1.20 `errors.Join` instead of `go.uber.org/multierr`

@dmathieu The patch looks great, thanks for doing this :) I think the problem I was pointing at above is not addressed by existing code. The problem is the difference...