This PR needs to be a broader discussion. If Zeppelin is going to support windows, that means making a commitment to support windows. That's means supporting a wider variety of configurations, and varying levels of user ability, orders of magnitude beyond what we do now. How are we going to CI test for what does and doesn't work on different Windows flavors? What about new features and changes that have dependencies that aren't available for Windows?
I suggest that if we move in this direction, we do so on a provisional basis -- for some period of time, say two releases, include the Windows code but say that Windows is in testing and not yet officially supported. That way, we can see what happens in-the-wild, and determine if we have the infrastructure to support it. > On Mar 17, 2016, at 3:08 PM, granturing <g...@git.apache.org> wrote: > > Github user granturing commented on the pull request: > > > https://github.com/apache/incubator-zeppelin/pull/734#issuecomment-198037337 > > I have no more changes. @dnldxn were you able to validate the latest > commit on your setup? > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket > with INFRA. > ---
