canmove, Confirmed users
737
edits
Jetpack/Module Deprecation Process: Difference between revisions
Jetpack/Module Deprecation Process (view source)
Revision as of 13:22, 29 August 2012
, 29 August 2012→Migration
| Line 19: | Line 19: | ||
During the deprecation period (default 18 weeks), the module will be in the deprecated state. | During the deprecation period (default 18 weeks), the module will be in the deprecated state. | ||
=== Support === | |||
We will track usage of deprecated modules on AMO and support developers migrating their code. | We will track usage of deprecated modules on AMO and support developers migrating their code. | ||
(Should we do more targeted outreach, especially for non-AMO add-ons?) | (Should we do more targeted outreach, especially for non-AMO add-ons?) | ||
=== Warnings === | |||
We will continue to provide warnings (will these happen automatically driven by the metadata?): | We will continue to provide warnings (will these happen automatically driven by the metadata?): | ||