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 722C4200B9C for ; Fri, 2 Sep 2016 07:22:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 70C0C160AB5; Fri, 2 Sep 2016 05:22:18 +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 B5D38160AB7 for ; Fri, 2 Sep 2016 07:22:17 +0200 (CEST) Received: (qmail 11834 invoked by uid 500); 2 Sep 2016 05:22:16 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 11630 invoked by uid 99); 2 Sep 2016 05:22:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2016 05:22:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D83361A7348 for ; Fri, 2 Sep 2016 05:22:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.299 X-Spam-Level: X-Spam-Status: No, score=0.299 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KuGoitGg4Pz7 for ; Fri, 2 Sep 2016 05:22:11 +0000 (UTC) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 34E1E5F3F3 for ; Fri, 2 Sep 2016 05:22:11 +0000 (UTC) Received: from mfilter28-d.gandi.net (mfilter28-d.gandi.net [217.70.178.159]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 0A8C6FB882 for ; Fri, 2 Sep 2016 07:22:05 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter28-d.gandi.net Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter28-d.gandi.net (mfilter28-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id T48lnSr4rw2K for ; Fri, 2 Sep 2016 07:22:02 +0200 (CEST) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.10] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id B5EABFB8A1 for ; Fri, 2 Sep 2016 07:22:02 +0200 (CEST) Subject: Re: [DISCUSS] Apache Falcon 1.0 To: dev@falcon.apache.org References: From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= Message-ID: <1c10eee2-0337-89f9-3add-573cb8aaca29@nanthrax.net> Date: Fri, 2 Sep 2016 07:22:02 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit archived-at: Fri, 02 Sep 2016 05:22:18 -0000 +1 It makes sense to prepare 1.0 release. Regards JB On 09/01/2016 04:55 PM, Ajay Yadava wrote: > Hello everyone, > > Now that 0.10 has been successfully released, thanks to heroic efforts of > Balu, I think it is time to start discussion on our long pending 1.0 > release :) I specifically want to discuss the following items. > > *Scope / Change Threshold for calling it 1.0* > > We need to decide on the bare minimum changes to call it 1.0 I know at > least 2 views on this in the community > > 1. First view is that 1.0 is all about API stability, Once we have > stabilized the existing API, we can call it 1.0. There are already some > changes committed to trunk like a new shell, moving post processing to > server side, REST API Revamp and some more lifecycle changes which will > definitely come in 1.0 This should be enough to do a meaningful 1.0 release. > 2. Another view is that we need to have lot of marketable features and > new capabilities to call it 1.0 so that we can publicize it enough and ask > audience to reconsider falcon even if they found Apache Falcon short for > their use cases. > > Please chime in with your thoughts :) > > > *Call for Volunteer* > > As discussed in last developer sync up, Pragya communicated to me that she > has very high work load at her office and will not be able to take out time > for release activities. If there are any committers who haven't yet done a > release and want to volunteer for 1.0, then please reply to this thread, > else I will assume the role of Release Manager for 1.0. Many release > activities require karma available only to committers, hence only > committers can volunteer. > > > Regards > Ajay Yadava > -- Jean-Baptiste Onofré jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com