Tagging about vroom-docker

[nilsnolde]

Ok, I don't care too much: I'll be in-sync with vroom core then and change the tagging description.

[nilsnolde]

Sure, it all depends on your release scheme for those two;) I thought it'd be nicer to pin vroom-express to a version for a vroom-docker version, but I do agree, it can add ambiguity in case of vroom core patches. Always using the newest master of vroom-express for a new vroom-docker release could also be ambiguous: we tag 1.10.0 here, then vroom-express gets an unrelated (to core) and important update with 0.9.0 or so; we'd have to wait until a new vroom release is made or you'd have to release a patch vroom version only to satisfy vroom-docker?

How about ditching semantic versioning instead and tag both repo versions, e.g. v1.9.0-v0.8.0, going forward?

[jcoupey]

My point is that the most important changes are on the vroom side. We don't have that many "important updates" for vroom-express. And they never wait for too long since core versions are released quite frequently.

[jcoupey]

This has been documented in the readme with #36.