Release 1.2.0

[korzio]

• Create a release ticket in github. Copy this checklist.
• Remove TODOs
• Make a release branch
• Document new state algorithm
• Add const docs
• Update Readme (supports draft-06)
• Add docs to npm ignore

VERSION="..."
VERSIONALPHA="$VERSION-alpha.0"
ISSUE="..."

git checkout -b release/$VERSION

• Update package.json version to $VERSIONALPHA and commit

git commit -m "release: Update package version to $VERSIONALPHA #ISSUE"

• Tag with the alpha version

git tag $VERSIONALPHA

• Publish test npm version $VERSIONALPHA

npm publish

• Check package internals - contains all required files (lib/, README.md, ./djv.js, package.json, ...), no extra files
• Check with updated json-schema test suite - check generated report
• Check speed metrics
• Update package.json version to $VERSION and commit

git commit -m "release: Update package version to $VERSION #ISSUE"

• Create a changelog

npm run changelog

• Tag $VERSION

git tag $VERSION

• Merge release branch to master (via github)
• Publish version $VERSION

npm publish

• Send update to gitter
• Update json-schema supports draft-06 description

[korzio]

Performance

Before

Validator	Relative speed	Number of test runs per second
djv	100%	24087 (± 2.15%)

After

Validator	Relative speed	Number of test runs per second
djv	100%	23386 (± 2.38%)

[korzio]

Validation Errors

Before

All validators fail this test

some languages do not distinguish between different types of numeric value, a float is not an integer even without fractional part

failed tests

Some validators have deliberately chosen not to support parts of the spec. Go to the djv homepage to learn if
that is the case for these tests.

test failed	reason
ECMA 262 regex non-compliance, ECMA 262 has no support for \Z anchor from .NET	Expected result: false but validator returned: true
validation of URIs, an invalid protocol-relative URI Reference	Expected result: false but validator returned: true
ref overrides any sibling keywords, ref valid, maxItems ignored	Expected result: true but validator returned: false
base URI change - change folder in subschema, number is valid	Expected result: true but validator returned: false
root ref in remote ref, string is valid	Expected result: true but validator returned: "Maximum call stack size exceeded"
root ref in remote ref, object is invalid	Expected result: false but validator returned: "Maximum call stack size exceeded"

All other tests passed.

After

All validators fail this test

some languages do not distinguish between different types of numeric value, a float is not an integer even without fractional part

All other tests passed.

[korzio]

json-schema-org/json-schema-org.github.io#158

[korzio]

https://gitter.im/korzio/djv?at=59cbc40bbac826f05406a37e