-
Notifications
You must be signed in to change notification settings - Fork 122
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
doc: add minutes for April 20, 2019 #523
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sam-github
commented
Apr 22, 2019
to how there is currently an ‘lts:’ tag). Sam: suggested this be opened as | ||
an issue in nodejs/release, because its an obviously sensible thing to do. | ||
* Ask the release team for a couple 2019 candidate dates that work well into | ||
their plans. Do this within the existing issue. |
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.
sam-github
commented
Apr 22, 2019
* Sam: Liran should give approval. | ||
* Some discussion of CVE allocation. We (Sam) should send Mitre an email | ||
saying we are going to be trying allocating CVEs through HackerOne, and if | ||
it goes well, we won’t need to be a CNA in 2020. |
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.
sam-github
force-pushed
the
wg-meeting-2019-04-22
branch
2 times, most recently
from
April 22, 2019 18:37
37dbec0
to
8b3f1d5
Compare
mhdawson
approved these changes
Apr 23, 2019
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
sam-github
force-pushed
the
wg-meeting-2019-04-22
branch
from
April 24, 2019 16:18
8b3f1d5
to
6a563fb
Compare
sam-github
force-pushed
the
wg-meeting-2019-04-22
branch
from
June 4, 2019 19:23
6a563fb
to
059834f
Compare
PR-URL: #523 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
sam-github
force-pushed
the
wg-meeting-2019-04-22
branch
from
June 4, 2019 19:24
059834f
to
9922ea9
Compare
patrickm68
added a commit
to patrickm68/security-wg-process
that referenced
this pull request
Sep 14, 2023
PR-URL: nodejs/security-wg#523 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
mattstern31
added a commit
to mattstern31/security-wg-process
that referenced
this pull request
Nov 11, 2023
PR-URL: nodejs/security-wg#523 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.