+1. Amazing work, guys. I'll set aside some time for a thorough review, but I definitely support bringing it to wider attention with an informal "Last Call" draft. -Brad On Tue, Apr 21, 2015 at 4:52 AM Mike West <mkwst@google.com> wrote: > I'm supportive of bringing this to last call. > > As an aside, I've reviewed a number of Joel's patches to implement the > current draft in Chrome, and that's looking pretty good. How are things > looking on the Mozilla side? Have you run into any blocking issues in the > current spec? > > -mike > > -- > Mike West <mkwst@google.com>, @mikewest > > Google Germany GmbH, Dienerstrasse 12, 80331 München, > Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der > Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth > Flores > (Sorry; I'm legally required to add this exciting detail to emails. Bleh.) > > On Tue, Apr 21, 2015 at 8:55 AM, Frederik Braun <fbraun@mozilla.com> > wrote: > >> The remaining open issues[1] on GitHub are mostly editorial nits. The >> technical parts should be well in place to advance to Last Call. >> >> I am aware of no fundamental controversies but would really like to get >> some wider attention on the spec. >> >> The current editor's draft is at >> <http://w3c.github.io/webappsec/specs/subresourceintegrity/>. >> >> >> The CfC will end in a week, that is April 28th, 2015. >> >> >> >> [1] >> < >> https://github.com/w3c/webappsec/issues?q=is%3Aopen+is%3Aissue+label%3ASRI+milestone%3ASRI-v1-LC >> > >> and >> < >> https://github.com/w3c/webappsec/issues?q=is%3Aopen+is%3Aissue+label%3ASRI+no%3Amilestone >> > >> >> >
Received on Tuesday, 21 April 2015 15:48:07 UTC