Confirmed users
1,158
edits
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
This page covers the 2017 planning process for the add-ons team. As we go through the planning process more details will be made here. It details the [https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ 2015 blog post] and the | This page covers the 2017 planning process for the add-ons team. As we go through the planning process more details will be made here. It details the [https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ 2015 blog post] and the [https://blog.mozilla.org/addons/2016/11/23/add-ons-in-2017/ 2017 plans]. | ||
== Timeline == | == Timeline == | ||
| Line 66: | Line 66: | ||
=== Will documentation on MDN about writing add-ons using legacy technologies be removed? === | === Will documentation on MDN about writing add-ons using legacy technologies be removed? === | ||
Yes, the focus will be on WebExtensions from now on and we’ll continue to point all pages over to WebExtensions. | Yes, the focus will be on WebExtensions from now on and we’ll continue to point all pages over to WebExtensions. | ||
=== Will add-ons continue to work on Firefox 52 ESR? === | === Will add-ons continue to work on Firefox 52 ESR? === | ||
Yes, we’ll support add-ons on Firefox 52 as long as that release is supported. | Yes, we’ll support add-ons on Firefox 52 as long as that release is supported. | ||