WebExtensions/DeprecationPolicy: Difference between revisions

← Older edit

WebExtensions/DeprecationPolicy (view source)

Revision as of 21:43, 25 October 2022

75 bytes added , 25 October 2022

Fix broken link formatting.

Robwu

47

edits

@@ Line 1: / Line 1: @@
 '''Status: draft'''
-From time to time we expect to be able to deprecate WebExtensions APIs. As of writing this document we haven't done that with any and aren't planning to. But it will likely happen one day.
+From time to time we expect to deprecate WebExtensions APIs.
 == Deprecating APIs ==
@@ Line 14: / Line 14: @@
 == Process ==
-* Discuss on dev-addons and other places as appropriate.
+* Discuss on the community forum and other places as appropriate.
-* Announce on the dev-addons mailing list with the subject "Intent to deprecate"
+* Announce on the forum "[https://discourse.mozilla.org/c/add-ons/announcements/107 Announcements]" category with the subject "Intent to deprecate"
 * Alter the addons-linter repository to warn developers using "web-ext lint" or AMO that the API is now deprecated.
 * Alter Firefox to output a warning to the browser console.
@@ Line 31: / Line 31: @@
 If there is a pressing security or privacy issue that a WebExtension API causes, then we would review and expedite that. Deprecation based on security would be on an as needed basis, but if it was deemed critical then most of the above would happen quickly and the block pushed to release as quickly as possible within the release management schedule.
-To report one of these please file a bug in bugzilla and set the security flag on the bug.
+To report one of these please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=WebExtensions:%20Untriaged&groups=toolkit-core-security file a bug in bugzilla and set the security flag on the bug].