Re: [spec-reviews] CSP (#42)

@mikewest - People are just noticing that the monolithic nature of CSP releases is in some ways hurting adoption; people (wrongly or rightly) feel they need to implement the entire version, and users feel they have to understand the entire new spec before using it.

Getting new features onto a release train can be frustrating too (e.g., `cookie-scope`)

Also, giving a new major version number to it when it contains compatible changes confuses many.

No concrete suggestions, but one straw-man would be to make the major versions of CSP only come out when there's a breaking change, and to allow other specs to define extensions. 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/42#issuecomment-143102301