On Tue, May 31, 2016 at 6:51 PM, Marcelo Vanzin <[email protected]> wrote:
> The document seems to imply that all source will live in the same > repository. Is that the goal? > > Because the main goal is to make these extensions to follow their "runtime" release and because we might end up having several extensions for a given "runtime", I was thinking on having one repository per "runtime" (e.g. Spark) which would make it easier to manage and release at the same time Spark releases for example. > My preference would be to have separate extensions live in separate > repos; that way, they can have their different release cycles that > might align better with the systems they're actually dependent on > (e.g. a Kafka extension releasing right after a new major Kafka > version). And one extension being unstable doesn't affect development > for other extensions. > > This brings a good point, but still, i think for management purposes, one repo might make things easier, and we could easily enable this by providing minor releases between runtime releases (e.g. bahir 2.0.0.1 when kafka 0.11 comes up but spark hasn't released 2.0.1 yet) Would that be ok for starting ? And I am sure we can re-evaluate moving to a repo per extension in the future. Thoughts ? -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
