Thanks for advice and can not agree more with you guys - as soon as I start developing a feature of the Zeppelin, simple branching model as you describe would be my first preference!
The code that I refer below though does not depend on or contain any part of Zeppelin itself. Basically it is a side-project of throw-away prototype for the IPC strategy, it never meant to be neither directly used nor merged to Zeppelin itself. Given that, although the benefit of visibility is huge, are you still advise project repo as the best place for it? -- Kind regards, Alexander On Thu, Jan 22, 2015 at 8:05 AM, Konstantin Boudnik <[email protected]> wrote: > +1 [a big one!] > > On Wed, Jan 21, 2015 at 02:50PM, Roman Shaposhnik wrote: > > On Wed, Jan 21, 2015 at 12:28 AM, Alex B. <[email protected]> wrote: > > > Quick update: I'v started to hack around a PoC for this feature here > > > https://github.com/bzz/zeppelin-multiprocess-interpreter-poc , it's > very > > > early stage but please feel free to check it out and provide any > feedback. > > > > > > On enabling\disabling this feature: if it will be easy to provide such > > > choice (which we are not sure yet) then there is no reason not to > implement > > > 4. > > > > You may want to consider developing features like this one directly in > > ASF repo on a feature branch. This is the model used by some of the > > most well established projects like Apache Hadoop, etc. It helps keep > > the work exposed to as many potential contributors as possible. > > > > Thanks, > > Roman. >
