Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6E536200CC9 for ; Mon, 17 Jul 2017 23:06:55 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6CC33165C53; Mon, 17 Jul 2017 21:06:55 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B3530165C4D for ; Mon, 17 Jul 2017 23:06:54 +0200 (CEST) Received: (qmail 51237 invoked by uid 500); 17 Jul 2017 21:06:54 -0000 Mailing-List: contact dev-help@fluo.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.incubator.apache.org Delivered-To: mailing list dev@fluo.incubator.apache.org Received: (qmail 51226 invoked by uid 99); 17 Jul 2017 21:06:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2017 21:06:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 79728180622 for ; Mon, 17 Jul 2017 21:06:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.522 X-Spam-Level: X-Spam-Status: No, score=-2.522 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id DG_QXOzltK_8 for ; Mon, 17 Jul 2017 21:06:52 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 1601B5FD81 for ; Mon, 17 Jul 2017 21:06:51 +0000 (UTC) Received: (qmail 51223 invoked by uid 99); 17 Jul 2017 21:06:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2017 21:06:51 +0000 Received: from mail-qk0-f178.google.com (mail-qk0-f178.google.com [209.85.220.178]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5B8A41A0029 for ; Mon, 17 Jul 2017 21:06:51 +0000 (UTC) Received: by mail-qk0-f178.google.com with SMTP id d78so1476483qkb.1 for ; Mon, 17 Jul 2017 14:06:51 -0700 (PDT) X-Gm-Message-State: AIVw111L3w1kGGed0nvUxSc/D1Wdt+qff2O/i/CJDID7vVyMmEMfwkVx ZIIeCsfroP3r2K7pUAGDafyTt26vyQ== X-Received: by 10.55.174.66 with SMTP id x63mr27919422qke.137.1500325610548; Mon, 17 Jul 2017 14:06:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mike Walch Date: Mon, 17 Jul 2017 21:06:40 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: New 'fluo-yarn' repo To: dev@fluo.incubator.apache.org Content-Type: multipart/alternative; boundary="94eb2c0617001074fe055489c723" archived-at: Mon, 17 Jul 2017 21:06:55 -0000 --94eb2c0617001074fe055489c723 Content-Type: text/plain; charset="UTF-8" There is no API but it might help users if the the 'fluo-yarn' command and fluo-yarn.properties file followed semver. On Mon, Jul 17, 2017 at 5:01 PM Keith Turner wrote: > On Mon, Jul 17, 2017 at 4:55 PM, Mike Walch wrote: > > I am not 100% sure about the versioning scheme but I don't think it > should > > match Fluo. The version is at 0.8.0 right now. I would like to make it > > 1.0.0 for first release and have the scripts and configuration files > follow > > semver. > > I like ver 1.0.0 for the first release. For semver, what will you > define as the API? > > > > > > On Mon, Jul 17, 2017 at 4:48 PM Christopher wrote: > > > >> Ah, I see. Seems like a good idea. Out of curiosity, what kind of > >> versioning scheme did you have in mind? > >> > >> On Mon, Jul 17, 2017 at 4:38 PM Mike Walch wrote: > >> > >> > Yes. Fluo-yarn will be on a different release schedule. A new > release > >> of > >> > Fluo should in most cases not require a new release of fluo-yarn. New > >> > releases of fluo-yarn will most likely be necessary to upgrade Apache > >> Twill > >> > to support newer releases of Hadoop YARN. > >> > > >> > On Mon, Jul 17, 2017 at 4:26 PM Christopher > wrote: > >> > > >> > > Is the idea to have fluo-yarn on a different release cycle? > >> > > > >> > > > >> > > On Mon, Jul 17, 2017 at 3:52 PM Mike Walch > wrote: > >> > > > >> > > > I would like to create new repo (called 'fluo-yarn') using Gitbox > to > >> > hold > >> > > > code for launching Fluo applications in YARN. This is related to > my > >> > > recent > >> > > > pull request [1]. Does anyone have any objections to this? > >> > > > > >> > > > [1]: https://github.com/apache/incubator-fluo/pull/883 > >> > > > > >> > > > >> > > >> > --94eb2c0617001074fe055489c723--