Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

New Release Plan #400

Closed
MylesBorins opened this issue Oct 11, 2019 · 7 comments
Closed

New Release Plan #400

MylesBorins opened this issue Oct 11, 2019 · 7 comments

Comments

@MylesBorins
Copy link
Contributor

MylesBorins commented Oct 11, 2019

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.

  • Land all changes including aside from unflagging on v13.x ASAP
  • Bring Divergent specifier hazard #371 to the TSC meeting next Wednesday specifically with the ask if we should delay the removal of the flag until we have a solution to "dual mode packages"
    • If the TSC is ok with unflagging we land the removal of the flag on 13.x and ship unflagged esm in 13.0.0
    • If the TSC would like us to spend more time on the problem before we unflag we don't unflag on 13.x and spend some time dedicated to that problem space
  • Backport all changes to 12.x aside from the flag removal
  • Assuming there is not major ecosystem push back we aim to remove the flag in the 1st or 2nd Semver Minor of 12.x LTS (likely in December or March)

Thoughts?

@jkrems
Copy link
Contributor

jkrems commented Oct 11, 2019

I think that sounds reasonable.

@targos
Copy link
Member

targos commented Oct 11, 2019

I think so too

@GeoffreyBooth
Copy link
Member

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 --experimental-modules one last thorough test before we unflag, to hopefully shake out as many bugs as possible before unflagging.

@mcollina
Copy link
Member

+1 to the plan. I would personally recommend to drop the flag in v13.

@kirkouimet
Copy link

@MylesBorins - As of Node 13.0.0 the flag is still required, correct?

@MylesBorins
Copy link
Contributor Author

MylesBorins commented Oct 23, 2019 via email

@GeoffreyBooth
Copy link
Member

See #408 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants