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

Steps required to upstream implementation #286

Closed
11 of 12 tasks
MylesBorins opened this issue Mar 4, 2019 · 2 comments
Closed
11 of 12 tasks

Steps required to upstream implementation #286

MylesBorins opened this issue Mar 4, 2019 · 2 comments

Comments

@MylesBorins
Copy link
Contributor

MylesBorins commented Mar 4, 2019

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?

@MylesBorins
Copy link
Contributor Author

If you have any thoughts or additions please chime in

@MylesBorins MylesBorins added the modules-agenda To be discussed in a meeting label Mar 4, 2019
@GeoffreyBooth
Copy link
Member

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)

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

2 participants