Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC #0364 - Tracking for Ember 2018 Roadmap #28

kategengler opened this issue Feb 12, 2019 · 2 comments


Copy link

commented Feb 12, 2019

RFC #0364 - Tracking for Ember 2018 Roadmap

Champion: @tomdale

Expand for Instructions

All teams need to consider a merged RFC to plan any required work. Each team should comment on or edit this with links to issues for the work (or a note to the effect of "No work required").

See the README for more information
See #3 for an example

Under each team, for each repo requiring work for the RFC under that team:
### [repo name](repo url)

- [ ] (issue or pr) description, (issue or pr) link

Remove Repos that do not apply, conversely, there will probably be other repos that need work and should be added.

Ember.js Team:

Ember CLI Team:

Ember Data Team:

Learning Team:

Steering Committee:


This comment has been minimized.

Copy link

commented Apr 26, 2019

@kategengler - I'm not sure exactly how to handle this one. It's not as clear cut to me as the others. Do we just make this the overarching "octane" tracking issue?


This comment has been minimized.

Copy link

commented Jun 13, 2019

@tomdale @rwjblue @kategengler we should figure this out so it doesn't happen to the 2019 Roadmap RFC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.