Re: Development model

Sounds good. Kind Regards, Corey Stubbs On Thu, Feb 2, 2017 at 9:50 AM Luciano Resende wrote: > I am not suggesting doing "everything" via SBT, just the basic compile, > test, build and package so that contributors used to other sbt based > projects fill comfortable

Re: Development model

I am not suggesting doing "everything" via SBT, just the basic compile, test, build and package so that contributors used to other sbt based projects fill comfortable getting started with the project. For all the other more optional/complex tasks, I am all for using a set of fully documented

Re: Development model

My typical development flow is to write code, run pip-release , and then install the pip release locally on my machine (pip install dist/toree-pip/pip-release; jupyter toree install), and test changes with the install. +1 on working on documenting the make targets. In terms of getting everything

Re: Development model

On Tue, Jan 31, 2017 at 9:56 AM, Marius van Niekerk < marius.v.niek...@gmail.com> wrote: > I think just documenting development workflow and process properly will > help a great deal. > Building Toree is a non-trivial exercise sadly. > > Completely agree that is a non-trivial exercise, but should

Re: Development model

I think just documenting development workflow and process properly will help a great deal. Building Toree is a non-trivial exercise sadly. On Tue, 31 Jan 2017 at 11:14 Luciano Resende wrote: > On Mon, Jan 30, 2017 at 5:47 PM, Jakob Odersky wrote: > > >

Development model

Hi everyone, I was wondering how everyone usually develops toree, specifically how changes to toree are tested with a jupyter notebook? I couldn't find any documentation on the website so I thought I'd ask here. I tried running the various makefile targets, including `make dev` and `make