3 ms·
What's the punchline? This post doesn't detail at all what's next for SemVer. What changes are coming? What's wrong with SemVer that needs fixing?
by garmaine 8y ago
What's the punchline? This post doesn't detail at all what's next for SemVer. What changes are coming? What's wrong with SemVer that needs fixing?
- steveklabnik 8y agoThis is an announcement that we have created a mechanism for making changes. It's now up to us (and anyone else submitting RFCs) to decide what changes are coming. I can't tell the future, only lay down those principles. As I said in my other comment, a lack of spec for ranges is a key addition that'll be coming.
- paulddraper 8y agoThey clearly have some deficiencies in mind; an example or two would go a long way toward helping this post.
- steveklabnik 8y agoI think that getting all of the implementations on the same page is possibly even more valuable than any changes. For example, since ranges aren't in the spec, npm and Cargo treat "1.2.3" very differently. Since we can't break either ecosystem, that means that that specific aspect will have to be either implementation-defined or "choose one of these two ways," but we can at least discover where these kinds of cases are, and possibly fix them, or properly spec them, as needed. This matters a lot for interoperability. For example, Notion is a Rust project that manages JavaScript stuff; for this to work, Rust's implementation will need a "do it like npm" flag. This is really tough when it's not even spelled out anywhere what the possibilities are. The lack of this causes more issues than real actual problems with the text as it is today, IMHO. For example, the Go code above requires a "v", which is not in the current spec, but some implementations handle it, some don't. Driving these things out is important!