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

Add information about release cadence to README.md #1830

Closed
wants to merge 1 commit into from

Conversation

gmlewis
Copy link
Collaborator

@gmlewis gmlewis commented Mar 25, 2021

With the recent requests for new releases, it would be nice to provide this FAQ in the README.md.

With the recent requests for new releases, it would be nice to provide this FAQ in the README.md.
@google-cla google-cla bot added the cla: yes Indication that the PR author has signed a Google Contributor License Agreement. label Mar 25, 2021
@gmlewis gmlewis requested a review from willnorris March 25, 2021 12:51
@codecov
Copy link

codecov bot commented Mar 25, 2021

Codecov Report

Merging #1830 (1370fcb) into master (94eb482) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1830   +/-   ##
=======================================
  Coverage   97.56%   97.56%           
=======================================
  Files         104      104           
  Lines        6602     6602           
=======================================
  Hits         6441     6441           
  Misses         87       87           
  Partials       74       74           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94eb482...1370fcb. Read the comment docs.

@willnorris
Copy link
Collaborator

are we just doing on-demand releases? I think the point I was making in #1280 was just about having a more predictable release schedule, not abandoning scheduled releases at all. That said, you're the one doing the bulk of the lifting here, so it's up to you if you want to try and do scheduled releases.

The most important part is that we set expectations appropriately, which this certainly does if this is the plan going forward.

@gmlewis
Copy link
Collaborator Author

gmlewis commented Mar 25, 2021

Well, it certainly is easier to perform on-demand releases from a maintenance perspective.

If you would prefer scheduled releases, what kind of schedule are you thinking?

@willnorris
Copy link
Collaborator

4-6 weeks?

@willnorris
Copy link
Collaborator

or even longer if there's not much new

@gmlewis
Copy link
Collaborator Author

gmlewis commented Mar 26, 2021

OK, sure, let's try that. I'll close this PR.

@gmlewis gmlewis closed this Mar 26, 2021
@gmlewis gmlewis deleted the release-cadence-readme branch October 18, 2022 00:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indication that the PR author has signed a Google Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants