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

chore(docs): splitting out "stable" feature flags by intent (config vs feature dev) #28016

Merged
merged 2 commits into from
Apr 17, 2024

Conversation

rusackas
Copy link
Member

SUMMARY

There was some discussion in Town Hall about whether or not we should use feature flags for runtime configuration or not. The jury is still out! No matter where they live, I figured that at least for now, we should split these up by intent. Then it's clearer to users whether these "stable" flags are ones that will remain (for now, anyway) as config, vs the ones that will march toward feature release and flag deprecation.

If this makes sense as a small intermediary step, let me know if I've miscategorized any of them :)

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@rusackas rusackas merged commit 8a390f0 into master Apr 17, 2024
28 checks passed
@rusackas rusackas deleted the further-clarification-around-flags branch April 17, 2024 15:29
qleroy pushed a commit to qleroy/superset that referenced this pull request Apr 28, 2024
jzhao62 pushed a commit to jzhao62/superset that referenced this pull request May 16, 2024
vinothkumar66 pushed a commit to vinothkumar66/superset that referenced this pull request Nov 11, 2024
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 4.1.0 labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/S 🚢 4.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants