On Wed, Sep 23, 2015 at 6:57 AM, Allen Wittenauer <[email protected]> wrote: > > > * versions tend to be tied to release artifacts: I think we're going to want > one artifact of everything rather than four different artifacts >
Any particular reason for this? It's easier to maintain our dist directory that way. Also fewer/less complicated VOTE threads needed. Actually, that might be enough to convince me. :) > * if we release often enough, it won't matter that much if one part hasn't > changed I had been thinking of this the opposite way; that if we release often we'll end up with many versions that are empty for some component (in particular audience-annotations). But I can't actually think of a problem with having "no changes in this release" in the release note section on one or more components. > * changes to the build system and repo layout will likely impact all > components anyway Are we going for a unified top-level build system? I hadn't even considered. We should look at how painful / not-painful things are over in Apache Avro then, since they're the closest I can think of in terms of having components with different build needs that have to be stitched together.
