I will will include this change in policy version 2.7.
- Wayne
On Wed, Mar 27, 2019 at 8:04 PM Ryan Sleevi wrote:
> I'm not sure whether it's necessary to indicate support, but since silence
> can sometimes be ambiguously interpreted: I support these changes and
> believe they achieve the desir
I'm not sure whether it's necessary to indicate support, but since silence
can sometimes be ambiguously interpreted: I support these changes and
believe they achieve the desired outcome.
___
dev-security-policy mailing list
dev-security-policy@lists.mozil
I'm [hopefully] beginning with a simple change that clarifies the language
used for Point-in-Time (PiT) audits used in policy. Section 3.1.3 of our
policy currently references a "point-in-time assessment", and section 8
uses the undefined abbreviation "PITRA", which stands for "point-in-time
readin
3 matches
Mail list logo