- From: Tobie Langel <tobie@fb.com>
- Date: Wed, 21 Mar 2012 22:41:13 +0000
- To: "public-w3process@w3.org" <public-w3process@w3.org>
So I'm late to this discussion and relatively new to W3C and standards in general. That said, there are countless examples in software, particularly in the open-source world--where the development process also happens publicly--, of versioning schemes solving this kind of problems quite elegantly. One of which I particularly like has even been specified here: http://semver.org/ Like most of the node community, I've been using SemVer for the past couple of years, and frankly, it's works really well. Couldn't we imagine something similar? Or is there resistance to using versioning tools for spec writing? Recommendation status would be akin to SemVer's 1.0. Editor's draft would follow a similar path to the pre-launch SemVer notation: breaking changes would get minor update (e.g. from 0.2.0 to 0.3.0), non-breaking changes would get patch updates. Minor and patch updates could be pushed to /tr immediately. The editor could go crazy on the bleeding-edge spec without affecting anyone yet the spec in /tr would be continuously updated. It's perfectly OK to tell me to shut-up and read the whole thread before commenting. I promise I won't insist. --tobie
Received on Wednesday, 21 March 2012 22:41:40 UTC