chore: 0.4.0 release proposal

[mayurkale22]

Which problem is this PR solving?

• Release note: https://github.com/open-telemetry/opentelemetry-js/releases/tag/untagged-2512ebd04df280a5dca2

• 67 File changed => 33 packages : 33 package.json + 32 version.ts (not applicable for test-utils)

• Dependendency : chore: rename registry to provider #749 (merged).

[codecov-io]

Codecov Report

Merging #751 into master will increase coverage by 3.83%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master     #751      +/-   ##
==========================================
+ Coverage   89.49%   93.33%   +3.83%     
==========================================
  Files         153       32     -121     
  Lines        5188      675    -4513     
  Branches      442       54     -388     
==========================================
- Hits         4643      630    -4013     
+ Misses        545       45     -500

Impacted Files	Coverage Δ
packages/opentelemetry-api/src/version.ts	0% <0%> (ø)	⬆️
...ges/opentelemetry-propagator-jaeger/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-scope-base/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-base/src/version.ts	0% <0%> (ø)	⬆️
...ckages/opentelemetry-plugin-mongodb/src/version.ts	100% <100%> (ø)
...y-api/test/noop-implementations/noop-meter.test.ts	97.22% <0%> (ø)	⬆️
...-api/src/context/propagation/NoopHttpTextFormat.ts	100% <0%> (ø)	⬆️
...opentelemetry-base/test/resources/resource.test.ts	100% <0%> (ø)	⬆️
...telemetry-scope-base/test/NoopScopeManager.test.ts	100% <0%> (ø)	⬆️
...opentelemetry-api/src/metrics/NoopMeterProvider.ts	100% <0%> (ø)	⬆️
... and 126 more

[dyladan]

Did you intentionally not update examples/getting started?

[mayurkale22]

Did you intentionally not update examples/getting started?

Yes, we can update that after the release.

[dyladan]

holding the approval until #749 is merged and included in this but overall LGTM

[OlivierAlbertini]

to merge after #747

[OlivierAlbertini]

Should we wait for

• chore: more advanced plugin configuration #628
• chore: rename registry to provider #749

?

#628 would also add breaking changes.

[mayurkale22]

Yes, I am waiting for #749. I am not sure about the current state of #628 /cc @dyladan

[dyladan]

Yes wait for #749

#628 should probably be closed. there is some talk in specs about making configuration mechanisms standardized across SIGs.

[mayurkale22]

holding the approval until #749 is merged and included in this but overall LGTM

@dyladan #749 merged into master, please review this PR.

[obecny]

this should not be released - all examples doesn't work because of api changes

[mayurkale22]

this should not be released - all examples doesn't work because of api changes

Waiting on #750

[dyladan]

Think this is good to go 🚀

[obecny]

#761 yet before that

[obecny]

Few questions with regards to

1. examples
2. getting started (versioning and still using registry instead of provider).
3. might be not related to this but do we already have "MeterProvider" instead of "MeterRegistry" ?

[mayurkale22]

Few questions with regards to ...

I think we have updated all the places (examples, getting-started etc.) to use latest code changes as per the master branch. I will update the examples version after the release.