RDB Shredder: turn into SBT submodule

[chuwy]

Both RDB Loader and RDB Shredder going to be released together (by lucky coincidence they both now versioned 0.12.0).

[BenFradet]

That's quite opportunistic, I like it 👍

[alexanderdean]

How will the versioning work - they will both share a unified version?

[chuwy]

That's an option that I consider. And that's what we're doing for elasticsearch (I suppose) and our another loader.

But it is possible to version them differently.

[BenFradet]

The situation is a bit different with the elasticsearch loader in that we support multiple es versions/apis but do the same thing (consume some stream and produce to es).

[chuwy]

Ok, I don't have a strong opinion on it. Right now I see that StorageLoader and Hadoop Shred shared very little and there was no point to share code between them, but on the other hand I can imagine things change significantly.

[alexanderdean]

If we have separate version numbers for each (which I'm not against), how do we version overall releases in this repo?

[chuwy]

I can imagine somewhat similar to JS Tracker's approach. 0.13.0 releases Loader 0.13.0, shredder/0.13.0 releases Shredder.

The only cons I see in same-version approach is that if we don't make any changes in Shredder in 0.x.0 release - asset still will be published on S3 without changes from previous version. We will have same assets with different versions.

[alexanderdean]

I think I am leaning towards independent version numbers, deployment per @chuwy's comment and Release N, Release N+1 in the release notes / CHANGELOG. But let me know what you two think...