Dev Feature Flag | Removal

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Content Dashboard
• Labels:
  • fc_22_06
• Epic Link: tango-blogsposts-content-dashboard
• Sprint: TANGO | #77 DEV | May09-Jun06, TANGO | #78 DEV | Jun06-Jun20

Checklist

#	What	Who	How
1	Remove the FF from the code	SW Engineer	https://github.com/liferay-tango/liferay-portal/pull/2403
2	Re-test if necessary	Testing Engineer	Mention the testing criteria followed

Testing Criteria

#	Feature Complexity	Testing Criteria
1	The new feature is completely modularized and has no outside dependencies	Low Risk Change: Once it has been tested behind the feature flagged, the flag can be removed and it is not needed to retest it.
2	The new feature is partially dependent on other frameworks, services, etc.	Retest again after removing the feature flag, because it may be possible that those dependencies got updated when the new feature was already tested and under a flag, thus leading to potential regressions. If the automated coverage is mature enough, checking the test results might be good enough. Otherwise, some manual testing should be done.
3	The new feature is highly dependent on other stuff	Retest some parts manually as the feature flag is removed.