Commit Graph

9 Commits

Author SHA1 Message Date
Vincent Batts 769176bbf8
version: bump master to -dev
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-09-08 09:56:55 -04:00
Vincent Batts 7dab1a245d
version: 1.0.0-rc2
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-09-08 09:55:21 -04:00
Vincent Batts 7d4fe7380f version: bump to -dev for master
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-06-03 15:47:55 -04:00
Vincent Batts 06479209bd version: v1.0.0-rc1
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-06-03 15:47:55 -04:00
Vincent Batts 54fba081a4 version: bump v0.6.0-dev
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-04-12 10:00:37 -04:00
Vincent Batts 78e6667ae2 version: v0.5.0
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-04-12 10:00:03 -04:00
Vincent Batts ab44e373ec version: bump v0.5.0-dev
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-03-10 18:54:08 +00:00
Vincent Batts 3ce138b193 version: v0.4.0
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-03-10 18:54:08 +00:00
Vincent Batts 7bf06d53dd source and schema: differentiate with examples
The standard is on the JSON schema (not yet IETF spec JSON-schema), such
that it is not implemenations specific. Thus far, the reference has been
in how golang source renders the JSON documents.

Having the JSON source and the markdown documents in sync has been an
ongoing step to keep in sync.

Separating these two allows the golang source to continue being _a_
reference, but the JSON schema in the documentation to be _the_
reference.

As validation tooling is refined, then it will facilitate ensuring
the available golang source conforms to the reference JSON.

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-03-09 19:18:20 +00:00