- From: Jake Archibald <notifications@github.com>
- Date: Mon, 02 Sep 2019 05:08:31 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 2 September 2019 12:08:53 UTC
@youennf > I wonder though what the benefits/goals of moving the v1 spec forward are if implementers and web developers will actually focus on the living standard. Is it more of a process kind of thing? Having two living specs has been a source of confusion for developers, which is why we ended up putting a big warning on https://w3c.github.io/ServiceWorker/v1/. Also, having to update both specs has made the editors reluctant to make substantial changes (eg, moving the cache API into its own spec). Going to CR is part of W3C's legal process, but I understand that once we've done that for V1, we can continue with a living standard, and get the same legal protection through automated snapshots, which don't involve the kind of formality we're having to go through here. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1458#issuecomment-527123990
Received on Monday, 2 September 2019 12:08:53 UTC