canmove, Confirmed users
737
edits
Jetpack/Module Deprecation Process: Difference between revisions
Jump to navigation
Jump to search
Jetpack/Module Deprecation Process (view source)
Revision as of 13:20, 29 August 2012
, 29 August 2012→Removal
(Created page with "{{draft|}} == Preparation == Before deprecating a module, we need to: * decide we want to deprecate it * develop and document an alternative * decide which release we want to d...") |
|||
| Line 32: | Line 32: | ||
The target removal date is 18 weeks after deprecation. In preparation for this date we'll decide whether we're happy to go ahead with removal: this will depend on how many users have successfully migrated from the deprecated module. | The target removal date is 18 weeks after deprecation. In preparation for this date we'll decide whether we're happy to go ahead with removal: this will depend on how many users have successfully migrated from the deprecated module. | ||
=== OK to remove === | |||
If we're happy to remove the module, we'll remove it and relocate it to a graveyard repository (URL?). | If we're happy to remove the module, we'll remove it and relocate it to a graveyard repository (URL?). | ||
| Line 39: | Line 41: | ||
* AMO blog | * AMO blog | ||
* mailing list | * mailing list | ||
=== Not OK to remove === | |||
If we're not happy with removal, we'll continue to support migration and target the next release. | If we're not happy with removal, we'll continue to support migration and target the next release. | ||