canmove, Confirmed users
737
edits
Jetpack/Weekly Meeting/2012-5-22: Difference between revisions
→Minutes
| (3 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
* Roundtable | * Roundtable | ||
** SDK versions used on AMO | ** SDK versions used on AMO | ||
** Scratchkit for executing code examples | |||
** Tags used in AMO Validator | |||
= AMO addons statistics = | = AMO addons statistics = | ||
| Line 32: | Line 34: | ||
= Minutes = | = Minutes = | ||
== Builder == | |||
No update. | |||
== SDK == | |||
We're releasing 1.8b2 today, is there anything that should be cherry-picked? | |||
* Alex: there are a few small fixes, probably nothing essential. | |||
* Will: there are a few docs additions, will send the list of commits. | |||
* Irakli: will check the set of commits and see if anything else should be taken. | |||
== Roundtable == | |||
=== Old SDK Versions === | |||
Alex has done an [https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2012-5-22#AMO_addons_statistics analysis of which SDK releases are being used in the Jetpack add-ons on AMO]. | |||
There are some old add-ons out there. | |||
* add-ons predating 1.0 have huge memory leaks | |||
* add-ons predating 1.0b5 use system principal in content scripts, which is a security problem | |||
* add-ons predatng 1.6.1 have some other big memory leaks. | |||
Should we attempt a repack of these old add-ons? Mossop: we should consider disabling add-ons that are a security risk. We should look at running a mass repack of old add-ons. The Daves will talk. | |||
=== scratchkit for executing code examples === | |||
Irakli demoed an [https://github.com/Gozala/scratch-kit add-on that turns code samples in the SDK docs into executable examples] using [http://blog.mozilla.org/devtools/2011/08/15/introducing-scratchpad/ scratchpad]- awesome! Would be great to integrate this into the SDK - this should happen when cfx.js lands, which is expected in Q2. | |||
=== AMO validator === | |||
Wes: the AMO validator downloads all tags, including beta versions and RCs as well as released versions, do we want this? It would be an easy fix to stop it happening. General agreement that this probably was not desirable behavior. | |||