he add-on not getting
> tested on nightly at all? Or at the same time as it goes to beta? When will
> it be used on release - when 46 ships as release, or earlier, or later?
>
> It also seems like you filed the privacy review after the functionality
> was implemented and is now shipping, which per
> https://wiki.mozilla.org/Privacy/Reviews seems like it is too late to
> incorporate meaningful feedback. I'm not on the privacy team, but that
> order looks wrong to me.
>
This is my fault – we began discussion of this collection many months ago
with people from data stewardship and legal through less formal channels,
and I didn't follow up with a formal privacy review bug. I agree it is not
the correct order.
Note that while implemented, the functionality is currently pref'd off.
--
Ian Bicking | Engineering Manager | Hello | Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Tue, Oct 9, 2012 at 11:41 PM, Boris Zbarsky wrote:
> On 10/10/12 12:23 AM, Ian Bicking wrote:
>
>> Here's how I think you'd write a simple XHR test in both:
>>
>> // SimpleTest aka MochiTest
>> req = new XMLHttpRequest();
>> req.open("GET&
On Tue, Oct 9, 2012 at 8:39 PM, Boris Zbarsky wrote:
> On 10/9/12 6:46 PM, Jonas Sicking wrote:
>
>> On Tue, Oct 9, 2012 at 2:43 AM, Aryeh Gregor wrote:
>>
>>> If it's a pain to write a particular file in testharness.js, it can be
>>> kept as mochitest. In my experience, quite a lot of tests bo
On Wed, Aug 22, 2012 at 3:38 PM, Gregory Szorc wrote:
> Let's think of what can be done to secure/limit Python. Disabling import
> has already been mentioned. That's a start.
>
> What about the ast module [1]? I /think/ it could be used to ensure parsed
> code conforms to whatever we allow. e.g.
4 matches
Mail list logo
