| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
|
nice job |
Sorry, something went wrong.
There was a problem hiding this comment.
May be s/v4.x/all maintained branches for timelessness. (we can add a link to https://github.com/nodejs/lts to explain what are those maintained branches)
Sorry, something went wrong.
There was a problem hiding this comment.
Also we can add a link to the upcoming backporting guide to the backporting part, doesn't need to happen in this PR though. Pending PR: #11099
Sorry, something went wrong.
There was a problem hiding this comment.
The lts project link should have a text. Maybe [the LTS page](https://github.com/nodejs/lts).
Also nit: 80-character wrap.
Sorry, something went wrong.
There was a problem hiding this comment.
Actuallyall maintained branches is probably clear enough(no need for the lts/v4.x part). The lts link can be attached to this phrase and the node.green tip can be placed in the parens.
Sorry, something went wrong.
There was a problem hiding this comment.
Oh uh..by s/v4.x/all maintained branches/ I meant "replace v4.x with all maintained branches"(sed syntax). Sorry for not being clear.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the correction, so "for the ease of backporting, it is encouraged to use those ES.Next features that can be used directly without a flag in [all maintained branches](https://github.com/nodejs/lts), you can check [node.green](http://node.green) for all available features in each release." will be better?
Sorry, something went wrong.
There was a problem hiding this comment.
Yep :)
Sorry, something went wrong.
There was a problem hiding this comment.
OK, updated 👍
Sorry, something went wrong.
|
@Trott might want to take a look at this? |
Sorry, something went wrong.
|
@nodejs/testing Seems A-OK to me. |
Sorry, something went wrong.
|
this would need a backport pr to land in v6 or v4 |
Sorry, something went wrong.
PR-URL: nodejs#11452 Refs: nodejs#11290 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Sorry, something went wrong.
|
@DavidCai1993 I'm noticing a backport to v4.x with a conflict, but no backport to v6.x. Would you be able to do v6 too? |
Sorry, something went wrong.
PR-URL: nodejs/node#11452 Refs: nodejs/node#11290 Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Update the writing-tests guide to restrict the ES.Next features usage in tests for the ease of backporting (only encourage to use those features that can be used directly without a flag in all maintained branches) .
Refs: #11290
Checklist
Affected core subsystem(s)
doc