On 24/10/2016 14:30, Julian Reschke wrote: > On 2016-10-24 15:10, Davide Giannella wrote: >> Wow, quite some replies :) >> ... >> However we still have the original problem to address: how are we >> planning to solve segment depending on oak depending on segment on third >> party applications? I have two proposals here that we could vote on if >> we want >> >> 1) Going back to monolithic? Read it as, segment-tar won't be released >> any more on its own cycle. >> >> 2) We correctly address dependencies. For example adding oak-core-api. >> ... > > If I had to do Oak releases, I'd clearly vote for 1) - this model has > drawbacks, but it's simple and easy to understand.
yes from a release pov it's way easier. However I'd like to ask to the people who decided to go for the independent segment-tar release. What's the rationale behind the decision? Why did we go in that direction that was not possible to do with a monolithic? Again, to be clear: I'm not championing neither one or the other solution. I simply would like to a a solution done properly, and hopefully quickly so that we ease our lives later on rather than complicate it. Davide
