Repository navigation
Feature flags #771
Copy link
Copy link
Closed
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
Description
Activity
It would be nice if we could apply the stability index to specific features, instead of at the module level.
I think basically all flagged features are unstable, everything else conforms to semver
#1159 for the first planned flagged feature
I like it! We should still increment the minors on such stuff, though.
@indutny of course. This is pretty much how I see it: http://emberjs.com/guides/configuring-ember/feature-flags/
We need some build and runtime infrastructure to make this possible
- addedmetaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
on Mar 24, 2015 - addeddiscussIssues opened for discussion and feedback.Issues opened for discussion and feedback.and removed
on Apr 28, 2015 A few features have gone in using flags at this point into various branches — uint8array-backed buffers in next, for example. I've opened an issue in the docs-repo-to-be; closing this one for now.
Edit: also, feature flags are a great idea 👏
Metadata
Metadata
Assignees
Labels
discussIssues opened for discussion and feedback.Issues opened for discussion and feedback.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.
We could wrap new features in feature flags that to could be enabled via command line flag or programmatically. That's what v8 does, Ember.js and maybe others. This way we could ship new features faster and reserve the right to change API for flagged features.
/cc @iojs/owners @iojs/collaborators