-
Notifications
You must be signed in to change notification settings - Fork 621
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
docs: re-write contributing guide #3748
Conversation
Co-authored-by: Yoshiya Hinosawa <[email protected]>
README.md
Outdated
While versioned independently of the Deno CLI, new minor versions of the | ||
Standard Library and the Deno CLI are published at the same time (every 6 | ||
weeks). Patch versions may be published in between. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't look correct to me (std always releases new minor versions even when CLI does patch releases), or do you suggest we should change the release pattern of deno_std?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, my misunderstanding. I didn't know this was the case. Either way, I thought this pattern didn't deviate too much from the current pattern. I'm not strongly opinionated, either way. My goal was to establish a predictable schedule while allowing us to move fast.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think this is all that's needed. Design and philosophy will come in another PR.