> On Sep 3, 2015, at 203PM, Bryan Thompson <br...@systap.com> wrote: > > I think that we could: > > 1. Release 3.0 on the shortest path consistent with appropriate QA. > 2a. Refactor the project structure into modules > 2b. Extend the project into interesting use case areas (IoT was discussed > recently). > > 2a and 2b could occur in parallel.
Generally agree (might disagree a bit on 2a and 2b concurrently). Big question for me though is as we release 3.0 (hopefully by end of 3Q - so this month) as a release candidate, and as we do bug fixes to approach a release, we’ll have to maintain both monolithic and modularized projects. Could be a pain. Do we also spin off a 2.2.2 modularization effort? > > A release with a project modular structure refactor would probably be > another major release (4.0). It will change the way people consume the > code. But it can happen as soon as the project has been modularized. (I > am going through this modular project pain right now in blazegraph.) > I’ve just been through this with 4 major projects I’m working with currently. I transitioned them from monolithic Ant projects with checked in binaries, to nimble Gradle projects that use great automation and dependency management. It was tough, but in the end totally worth it. Good luck :) Regards Dennis
