Skip to content

Update README to remove WIP and clarify blueprint status #136

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.

Sign up for GitHub

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

Merged
NullVoxPopuli merged 1 commit into from
Apr 7, 2026
Merged

Update README to remove WIP and clarify blueprint status #136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,8 @@ For migrating a v1 addon to a v2 addon, you may follow _[Porting Addons to V2](h
this blog post [Migrating an Ember addon to the next-gen v2 format
](https://www.kaliber5.de/de/blog/v2-addon_en).

## WIP

This is still work in progress but we are aiming for this to be the new default for when someone generates an addon with `ember addon super-addon-name`. This will need an RFC to change the default but if you notice anything that you would like to be improved with this blueprint please open an issue to discuss, you don't need to wait for the RFC process to give us feedback.
> [!NOTE]
> This is not yet the default blueprint. For discussion on strategy around this becoming the default, see [the RFC](https://github.com/emberjs/rfcs/pull/985)

## Usage

Expand Down
Loading