Prepare for about solidity-coverage

[area]

I believe it is a special case for major version 0, yeah, I'll try and find an authoritative source for that when I'm out of this meeting 😛

[cgewecke]

@area I published testrpc-sc v4 to npm and added you as owner. (I used a non-master branch to do this, in the hope of causing as little damage as possible)

Also updated master here to use the new rpc after testing it on Open Zeppelin (it works). And there's a new doc about testrpc / vm stuff.

RE: publishing here - there's absolutely no rush, but I'm wondering if the safest course is to go up a major version, mostly because the way testrpc 4 is invoked from node_modules has changed and people have been running it on its own with norpc set to true. Anyone floating on a caret would be insulated from that difference.

[area]

Following semver, people matching against ^0.1.x will not be upgraded to 0.2.0 if the latter is released (if major version is 0, minor version indicates breaking changes):

> semver -r ^0.1.10 0.1.11 0.2
0.1.11

[cgewecke]

Oh good! Is that a special case for 0 prefixed releases? I looked at Stack Overflow when wondering what to do here and saw this.

In the simplest terms, the tilde matches the most recent minor version (the middle number). ~1.2.3 will
match all 1.2.x versions but will miss 1.3.0.

The caret, on the other hand, is more relaxed. It will update you to the most recent major version (the first
number). ^1.2.3 will match any 1.x.x release including 1.3.0, but will hold off on 2.0.0.

Is that incorrect?

[area]

https://github.com/npm/node-semver#caret-ranges-123-025-004

[cgewecke]

Thanks! I had no idea about that. Minor it is . . . I'll publish today unless you see things that should be fixed.

[cgewecke]

v0.2.0

[cgewecke]

Oooooh. I just watched Greenkeeper open a PR upgrading to latest at Gnosis and it passed. 🦉