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

Change the go version schedule. #3078

Conversation

MadVikingGod
Copy link
Contributor

Closes #2918

This changes our readme to reflect the go version schedule agreed on in the SIG.

@codecov
Copy link

codecov bot commented Aug 9, 2022

Codecov Report

Merging #3078 (1c22fcc) into main (eb55e60) will increase coverage by 0.0%.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##            main   #3078   +/-   ##
=====================================
  Coverage   76.2%   76.2%           
=====================================
  Files        179     179           
  Lines      11939   11939           
=====================================
+ Hits        9103    9105    +2     
+ Misses      2596    2594    -2     
  Partials     240     240           
Impacted Files Coverage Δ
sdk/trace/batch_span_processor.go 81.9% <0.0%> (+0.8%) ⬆️

@MadVikingGod MadVikingGod added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Aug 9, 2022
@MadVikingGod
Copy link
Contributor Author

closing in favor of #3079

@MrAlias
Copy link
Contributor

MrAlias commented Aug 9, 2022

Gah, my bad. Just seeing this 🤦

@MadVikingGod MadVikingGod deleted the mvg/reword_version_schedule branch August 11, 2022 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Is the cool-off time between go versions right?
2 participants