Inada Naoki

While proposal have version number, it's not a version of spec. All of proposal (v1, v2, ... v5) is for "new spec".

> But what version is the current spec? "Current" or "New". > Where are the old versions of the spec? https://github.com/msgpack/msgpack/blob/master/spec-old.md > Why is there no version numbering in the...

FYI, new spec doesn't deprecate data created by old spec. Decoders based on new spec can decode data encoded by encoders based on old spec. Incompatible changes can't happen in...

JSON also doesn't version number. Do you hesitate using JSON?

Proposal is proposal, not a spec.

@frsyuki How about "old" and "final" as version scheme?

When giving version scheme, we should separate "format" and "spec". JSON format is stable, but have some specs (ECMA-404, RFC4627, RFC7158 and RFC 7159). msgpack format is stable now, but...

FYI, `https://github.com/msgpack/msgpack/blob/master/spec.md` is always describe final format. tag is not required to refer format.

> When I today implement the current master and the spec is changed over a few month, my products specification implicitly change, but my implementation won't magically change. Do you...

> This states a major of 0, and a minor of 6. > And this states a major of 1, and a minor of 1. It's a library (msgpack-c) version,...