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

Octane Tracking Issue #17234

Open
MelSumner opened this Issue Nov 28, 2018 · 15 comments

Comments

@MelSumner
Copy link
Contributor

MelSumner commented Nov 28, 2018

Goal

The purpose of this issue is to provide an overall issue to track the status of the work necessary to ship the Octane Edition of Ember.js.

If anyone wants to work on any of the items in this list, please check in the #st-octane channel of our Discord chat first.

The following to-do list will be updated to include links to individual issues as they are created. The issues themselves will contain more details for each item on this list. We have roughly tried to give them some sort of priority order, but anticipate that most of the work can be done in parallel.

To Do

Finish What We Started (1 of 7)

As per the 2018 Roadmap, there is commitment and focus to finishing the things we've already started.

New RFCs to write (2 of 7)

RFC's to Review/FCP/Merge (3 of 7)

Implementation (4 of 7)

Documentation (5 of 7)

Stretch Goals (6 of 7)

These are items that have been de-scoped or were never originally planned, but are now being tracked as stretch goals.

  • Svelte Builds (the last code cleanup easily allowed this item to become a stretch goal)

PM Notes/Planning (7 of 7)

  • set up octane strike teams in each of the relevant Ember orgs:
  • discussion: ember wizard (like ember-cli-create)
    • @rwjblue to discuss with ember-cli team
  • discussion: track stretch goals?
  • discussion: track de-scoped (and why) items - yes
  • discussion: tracking the website update project
  • discussion: what scope creep items are we noticing? what should be included in the next edition of Ember?
  • need: call for more community members to join in on Octane work

Post-Octane:

  • Add Octane blueprint as the default to ember-cli once it's determined that it works as intended
@tomdale

This comment has been minimized.

Copy link
Member

tomdale commented Dec 4, 2018

@MelSumner We should track the build pipeline improvements in https://github.com/embroider-build/embroider as well.

@oligriffiths

This comment has been minimized.

Copy link

oligriffiths commented Dec 5, 2018

@MelSumner https://broccoli.build and https://github.com/broccolijs/broccolijs.github.io for the new broccoli site and docs

@knownasilya

This comment has been minimized.

Copy link
Contributor

knownasilya commented Dec 6, 2018

Tracked properties RFC can be checked off and link updated.

@tomdale

This comment has been minimized.

Copy link
Member

tomdale commented Dec 11, 2018

We talked about auditing what gets included in the default app blueprint. See related issues:

  1. ember-cli/ember-cli#6294
  2. ember-cli/ember-cli#7760
@rwjblue

This comment has been minimized.

Copy link
Member

rwjblue commented Dec 11, 2018

FWIW, @tomdale that seems quite orthogonal to the Octane Edition to me (not saying we shouldn't be more careful and have better checks/balances, just that its not related to octane at all)...

@mike-north

This comment has been minimized.

Copy link
Contributor

mike-north commented Dec 11, 2018

its not related to octane at all

My reasoning for bringing this up recently is that a default blueprint that supports multiple programming models (i.e., a future default octane blueprint) may include extra cruft that a pure "classic" app or pure "octane" app doesn't need at all.

If we can validate that this is not a concern, I agree that this isn't very closely related to octane

@NullVoxPopuli

This comment has been minimized.

Copy link
Contributor

NullVoxPopuli commented Dec 11, 2018

imo, the octane blueprint, https://github.com/ember-cli/ember-octane-blueprint should be the ideal brand new / shiny app. I don't think the old programming model should be involved in the blueprint. :-\

@rwjblue

This comment has been minimized.

Copy link
Member

rwjblue commented Dec 23, 2018

@MelSumner - I think we need to get some MU related things here in this checklist (I don't spot any, but AFAICT MU is still considered part of the octane feature set...).

@gossi

This comment has been minimized.

Copy link

gossi commented Dec 23, 2018

It's already been called Octane layout instead of MU layout ... and the more I think about it the more it makes sense!

@MelSumner

This comment has been minimized.

Copy link
Contributor

MelSumner commented Jan 2, 2019

@MelSumner - I think we need to get some MU related things here in this checklist (I don't spot any, but AFAICT MU is still considered part of the octane feature set...).

@rwjblue we linked to the MU quest issue in the first section- "Finish What We Started" - is there more that you think we should track?

@gossi

This comment has been minimized.

Copy link

gossi commented Jan 7, 2019

Regarding ember-cli-create I put this issue together: ember-cli/ember-cli#8343. Depending on how much of the embroider spec will be implemented as part of octane (= publication format), the issue I linked is mainly speaking about the authoring format which can be complementary to the publishing format.

Personally, I wouldn't see ember-cli-create as part of octane while the authoring format could be (which basically sets the foundation for ember-cli-create).

Let me know, if that would make a good addition or better postpone it to post-octane release or how I can help with that.

@NullVoxPopuli

This comment has been minimized.

Copy link
Contributor

NullVoxPopuli commented Jan 9, 2019

octane blueprint > move addon to ember-cli org can be checked off :)

@jenweber

This comment has been minimized.

Copy link
Contributor

jenweber commented Jan 12, 2019

Update, here's a quest issue for tracking the Angle Brackets conversion in the guides ember-learn/guides-source#139

@simonihmig

This comment has been minimized.

Copy link
Contributor

simonihmig commented Jan 12, 2019

The Remove jQuery RFC can be checked off!
I also created a tracking issue, which we can link to maybe: #17476

@mike-north

This comment has been minimized.

Copy link
Contributor

mike-north commented Jan 15, 2019

User story around feature flags and optional features, as it pertains to the octane blueprint

As a workshop instructor, I need to know the default values for various optional/feature flags in the octane blueprint, in order to understand concretely what my students will get when they run ember new, and build material around ember new that remains valid over a significant period of time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment