This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 2, 2023. It is now read-only.
Steps required to upstream implementation #286
Description
Activity
If you have any thoughts or additions please chime in
I’m working on the docs update and I can help write the blog post copy (and be involved in messaging). I’ll need help with some of the sections of the docs, please let me know if anyone would like to help with this.
This might be a good time to start paying attention to our project board. 😄 (thanks @SMotaal)
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?