@MylesBorins is there a document or post somewhere which describes the process for managing Node.js’ releases vis-a-vis branches, tags, cherry-picking, etc?
-
-
-
Replying to @bitandbang @b0neskull
https://github.com/nodejs/node/blob/master/doc/releases.md … https://github.com/nodejs/node/blob/master/doc/guides/backporting-to-release-lines.md … /Cc
@gibfahn in case I missed anything2 replies 0 retweets 3 likes -
is there anything that automates the addition of PR-URL?
2 replies 0 retweets 1 like -
Replying to @b0neskull @MylesBorins and
wow, it’s incredibly awkward to work backwards from a commit to figure out what PR it came from.
1 reply 0 retweets 1 like -
Doesn't the pr url just tell you that?
1 reply 0 retweets 2 likes -
no, rather, I mean, without it
1 reply 0 retweets 2 likes -
Yes I've started including a PR link in all my commits, just because the #54 style link in other GitHub repos stops being useful if you move the repo somewhere else. Also when people use the default Github merge, only the top commit gets that link.
1 reply 0 retweets 1 like -
Replying to @gibfahn @b0neskull and
Metadata can be auto-generated by `git node metadata`: https://github.com/nodejs/node-core-utils/blob/master/docs/git-node.md#git-node-metadata …
2 replies 0 retweets 1 like -
ahhha! this is (I think) what I’m looking for. the “why” behind all my questions is: I’m wondering what of this process/toolkit I can adopt/steal for my own projects. which makes sense, what needs extra tooling, etc
2 replies 0 retweets 1 like
Sounds like nodejs/node-core-utils might be helpful for you. FWIW I'm sure the node-core-utils team would be in favour of making it work with other projects too, raise an issue!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
