-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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: Remove CROSS_REFERENCES feature flag #21815
Conversation
Codecov Report
@@ Coverage Diff @@
## master #21815 +/- ##
==========================================
- Coverage 66.93% 66.93% -0.01%
==========================================
Files 1805 1805
Lines 69066 69058 -8
Branches 7369 7366 -3
==========================================
- Hits 46227 46221 -6
+ Misses 20932 20931 -1
+ Partials 1907 1906 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
We also need to remove the flag from |
/testenv up |
@jinghua-qa Ephemeral environment spinning up at http://34.218.244.229:8080. Credentials are |
/testenv up |
@geido Ephemeral environment spinning up at http://35.85.138.179:8080. Credentials are |
…e/rm-crossreferences-feat-flag
Feature Acceptance Test passed for crud views. I will be merging this PR once the FAT for Explore is also confirmed |
@@ -466,7 +466,6 @@ def _try_json_readsha(filepath: str, length: int) -> Optional[str]: | |||
"EMBEDDABLE_CHARTS": True, | |||
"DRILL_TO_DETAIL": False, | |||
"DATAPANEL_CLOSED_BY_DEFAULT": False, | |||
"CROSS_REFERENCES": False, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the preferred strategy to first enable the CROSS_REFERENCES
feature by default and then deprecate the feature in version 3.0?
Also SIP-57 changing the default or removing a feature flag is deemed a breaking change and thus the appropriate actions need to be undertaken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one is a little funny, because the feature flag never went out in a version, and will not. So adding and removing it between published versions was perceived as a non-issue. We were hoping to implement a good means of launching darkly using this sort of ephemeral feature flag in lieu of a giant feature branch. Perhaps if we need to do this again, we can add a new category of "Pending release" or something to FEATURE_FLAGS.md to explain these?
I'll bring this up in Town Hall, and be seeking more opinions in general, but hopefully we can let this one through since the FF was never released or intended to be released.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the context @rusackas. This SGTM.
/testenv up |
@jinghua-qa Ephemeral environment spinning up at http://35.86.76.39:8080. Credentials are |
Validated in the recent ephemeral env that the search issue is fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Ephemeral environment shutdown and build artifacts deleted. |
SUMMARY
This PR removes the CROSS_REFERENCES feature flag as the feature will be enabled by default.
Approval from QA is required before merging this PR
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
N.A
TESTING INSTRUCTIONS
All the tests should pass
ADDITIONAL INFORMATION