Skip to content

Conversation

haqer1
Copy link
Contributor

@haqer1 haqer1 commented Apr 1, 2020

…sed to sign a release could be a sub-key of a key listed in README(.md) (which itself isn't listed in it)

Update README.md.

Fixes: #32559

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Apr 1, 2020
…sed to sign a release could be a sub-key of a key listed in README(.md) (which itself isn't listed in it)

Update README.md.

Fixes: nodejs#32559
…d to import a key used to sign a release & check whether it is a sub-key of a primary key listed in README(.md) (which itself isn't listed in it)...

Addition README.md update

Fixes: nodejs#32559
@haqer1 haqer1 force-pushed the signing-key-fixup-alternative-approach-2 branch from 9949a61 to fa68553 Compare April 1, 2020 05:10
Copy link
Member

@addaleax addaleax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@MylesBorins MylesBorins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I think it is reasonable to mention subkeys in this section I think the currently proposed copy could be more succinct.

I've made proposed an alternative but am also willing to review another iteration. Not blocking current copy, but I do think there is room for improvement.

haqer1 and others added 2 commits April 4, 2020 15:48
@haqer1 haqer1 force-pushed the signing-key-fixup-alternative-approach-2 branch from 0e9ab47 to 333072c Compare April 4, 2020 09:50
@haqer1
Copy link
Contributor Author

haqer1 commented Apr 4, 2020

I've committed the suggested changes to simplify landing of this PR (part 1).

That said, i think part 2 is needed:
either PR #32654 or PR #32655.

Copy link
Contributor

@MylesBorins MylesBorins left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

MylesBorins pushed a commit that referenced this pull request Apr 14, 2020
PR-URL: #32591
Fixes: #32559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
@MylesBorins
Copy link
Contributor

Landed in ee5c836

MylesBorins pushed a commit that referenced this pull request Apr 17, 2020
PR-URL: #32591
Fixes: #32559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
targos pushed a commit to targos/node that referenced this pull request Apr 25, 2020
PR-URL: nodejs#32591
Fixes: nodejs#32559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
BridgeAR pushed a commit that referenced this pull request Apr 28, 2020
PR-URL: #32591
Fixes: #32559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
@BridgeAR BridgeAR mentioned this pull request Apr 28, 2020
targos pushed a commit that referenced this pull request Apr 28, 2020
PR-URL: #32591
Fixes: #32559
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
6 participants