This repository was archived by the owner on Sep 2, 2023. It is now read-only.
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Steps required to upstream implementation #286
Closed
Description
Following last weeks meeting I think we are really close to be able to upstream our new implementation to core.
Important Dates:
March 13th:
Date of next Modules meeting. Intent to approve implementation to be sent upstream
March 20th:
Date to open Pull request upstream to begin getting reviews
March 27th:
Date to review upstream concerns if necessary.
April 4th:
Target date to land upstream. Subject to change, could land sooner if no changes necessary.
April 11th:
Go / No Go date. If we cannot reach consensus upstream we will likely be unable to merge for 12.x after this date.
April 23rd:
Targeted release date for v12.x
What needs to get done?
- Finalize Phase 2 in planning document
- loaders #287
- extension / folder resolution Update Phase 2 file extension/directory index searching plan #288
- implementation of missing phase two features
- Re add upstream loader nodejs/ecmascript-modules#47
- extensions / folder resolution nodejs/ecmascript-module#48
- Update Documentation to reflect latest implementation
- Final code + test + doc review
- Determine messaging around upstream PR
- Open Upstream PR
- Write copy about what our group has been doing and the current progress and status for public blog post
Metadata
Metadata
Assignees
Labels
No labels