Change Details

Abstract: > One of MediaWiki's greatest strengths is the diverse extension ecosystem. But we (MediaWiki core developers) can often make it hard for extension developers to keep up with constant breaking changes. We do not have a standard deprecation policy, leading to widely inconsistent practices depending on who writes and/or reviews the patch. Some reviewers expect you to fix all instances in Gerrit before merging a core deprecation patch, others will be fine with fixing none. For more: https://www.mediawiki.org/wiki/Requests_for_comment/Deprecation_policy ----- **See Also:** {T114384} {T149727} {T146965} {T115341}

Abstract: > One of MediaWiki's greatest strengths is the diverse extension ecosystem. But we (MediaWiki core developers) can often make it hard for extension developers to keep up with constant breaking changes. We do not have a standard deprecation policy, leading to widely inconsistent practices depending on who writes and/or reviews the patch. Some reviewers expect you to fix all instances in Gerrit before merging a core deprecation patch, others will be fine with fixing none. For more: https://www.mediawiki.org/wiki/Requests_for_comment/Deprecation_policy ----- **See Also:** {T114384} {T149727} {T115341}

Abstract: > One of MediaWiki's greatest strengths is the diverse extension ecosystem. But we (MediaWiki core developers) can often make it hard for extension developers to keep up with constant breaking changes. We do not have a standard deprecation policy, leading to widely inconsistent practices depending on who writes and/or reviews the patch. Some reviewers expect you to fix all instances in Gerrit before merging a core deprecation patch, others will be fine with fixing none. For more: https://www.mediawiki.org/wiki/Requests_for_comment/Deprecation_policy ----- **See Also:** {T114384} {T149727} {T146965} {T115341}