Change Details

== Background In 2019 we disabled the mobile beta (T237290) Since then we have been maintaining a large amount of code (1000+ lines) that impacts user performance for no good reason. The beta mode has not been used for 6 years, so restoring it at this point would come with considerable risk. We should be responsible and remove all this code. You can enable the beta mode locally with ``` $wgMFEnableBeta = true; $wgMFBetaFeedbackLink = true; ``` Do this before working on this ticket!! == User story - As a developer I don't want to maintain unused code - As a user I don't want to download unnecessary code. == Requirements [] The beta mode option and feedback option is removed from includes/specials/SpecialMobileOptions.php. Make sure you can see it before working on the changes needed to remove it! [] The $wgMFEnableBeta and MFBetaFeedbackLink feature flag is removed from extension.json and README is updated. [] Minerva skin repo is updated to remove the reference to MFEnableBeta [] All feature flag configuration in extension.json which features `"beta": true` is updated to not include it. For context feature flags in MobileFrontend express a mode and then whether the feature is enabled so once beta is removed these are inactive and doing nothing. [] includes/Features/BetaUserMode.php is removed [] The method MobileContext::isBetaGroupMember is removed [] Any code checking `isBetaGroupMember` to be truthy is eliminated. [] ` $vars['wgMFMode']` should be set to `'stable'` unconditionally. This is how many extensions detect if the mobile site is running so must be kept intact. === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - Add mockups and design requirements == Acceptance criteria - Add acceptance criteria == Communication criteria - does this need an announcement or discussion? - Add communication criteria == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //

== Background In 2019 we disabled the mobile beta (T237290) Since then we have been maintaining a large amount of code (1000+ lines) that impacts user performance for no good reason. The beta mode has not been used for 6 years, so restoring it at this point would come with considerable risk. We should be responsible and remove all this code. You can enable the beta mode locally with ``` $wgMFEnableBeta = true; $wgMFBetaFeedbackLink = true; ``` Do this before working on this ticket!! == User story - As a developer I don't want to maintain unused code - As a user I don't want to download unnecessary code. == Requirements [] The beta mode option and feedback option is removed from includes/specials/SpecialMobileOptions.php. Make sure you can see it before working on the changes needed to remove it! [] The $wgMFEnableBeta and MFBetaFeedbackLink feature flag is removed from extension.json and README is updated. [] Minerva skin repo is updated to remove the reference to MFEnableBeta [] All feature flag configuration in extension.json which features `"beta": true` is updated to not include it. For context feature flags in MobileFrontend express a mode and then whether the feature is enabled so once beta is removed these are inactive and doing nothing. [] includes/Features/BetaUserMode.php is removed [] The method MobileContext::isBetaGroupMember is removed [] We remove the codeAny code checking `isBetaGroupMember` to be truthy is eliminated. [] All references to config have been removed` $vars['wgMFMode']` should be set to `'stable'` unconditionally. This is how many extensions detect if the mobile site is running so must be kept intact. === BDD - For QA engineer to fill out === Test Steps - For QA engineer to fill out == Design - Add mockups and design requirements == Acceptance criteria - Add acceptance criteria == Communication criteria - does this need an announcement or discussion? - Add communication criteria == Rollback plan - What is the rollback plan in production for this task if something goes wrong? //This task was created by Version 1.2.0 of the [[ https://mediawiki.org/w/index.php?title=Reading/Web/Request_process | Web team task template ]] using [[ https://phabulous.toolforge.org/ | phabulous ]] //