Kerrick Long

I've noticed that _some_ colors can be customized by customizing `--tblr-primary` at the `:root` level, but others (such as those [here](https://github.com/tabler/tabler/blob/dc8cad144a05afb443a10bfa8a803e430d54c8e5/src/scss/layout/_navbar.scss#L228)) cannot. I, too, would love universal support for a...

> This RFC (as written), suggests that we would never issue deprecations for private APIs, because the act of issuing a deprecation means that an API is public. This might...

> This also means that churn goes way up, because with "GC" releases occurring far more frequently the time between deprecation and removal becomes very short. It doesn’t. If a...

And as I mentioned in the RFC, the “until” date can be a minimum version, not a maximum. They can stick around past that version.

I had never considered that lockstep releases could be the root cause of the issues that caused me to write this RFC. That’s an interesting perspective...

What's the best way to move forward with the ideas presented in this RFC and/or the discussion on this PR?

It's unclear to me from the RFC, but will Semantic Versioning be respected in `@ember/core`? Given the given example from the RFC, let's assume Ember 3.2.0 is released and it...

> When you run the upgrade command, it will edit your package.json such that the newly split packages are included in your package.json by default, so it behaves exactly the...

> This is a misunderstanding of semver. If it's a misunderstanding of semver, it is likely a common one. Everything from third-party tools like David DM and GreenKeeper to the...

> But the goal here is to enable a whole new class of apps to become Ember users. Apps that today would not have chosen Ember because it's "too big"...