This repository has been archived by the owner on Sep 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 43
New Release Plan #400
Comments
I think that sounds reasonable. |
I think so too |
Agreed, and I think once we settle exactly what the plan is (get a response from the TSC etc.) I think we should announce the expected release version and date, perhaps in another Medium post. That would invite the public to give |
+1 to the plan. I would personally recommend to drop the flag in v13. |
@MylesBorins - As of Node 13.0.0 the flag is still required, correct? |
Yup
…On Wed, Oct 23, 2019, 2:36 PM Kirk Ouimet ***@***.***> wrote:
@MylesBorins <https://github.com/MylesBorins> - As of Node 13.0.0 the
flag is still required, correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#400?email_source=notifications&email_token=AADZYV7UKTDN5R3QG3XCLXLQQCKTZA5CNFSM4I73OH62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECCOFDI#issuecomment-545579661>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADZYV73MBS4LR3QYT3QBZLQQCKTZANCNFSM4I73OH6Q>
.
|
See #408 (comment). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As per #399 (comment) it seems like folks are not comfortable with unflagging modules on LTS without it having lived in a current release for sometime. So here is a suggestion for an alternative path forward.
Thoughts?
The text was updated successfully, but these errors were encountered: