Return-Path: X-Original-To: apmail-fineract-dev-archive@minotaur.apache.org Delivered-To: apmail-fineract-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B980718002 for ; Thu, 7 Jan 2016 18:13:52 +0000 (UTC) Received: (qmail 84875 invoked by uid 500); 7 Jan 2016 18:13:52 -0000 Delivered-To: apmail-fineract-dev-archive@fineract.apache.org Received: (qmail 84842 invoked by uid 500); 7 Jan 2016 18:13:52 -0000 Mailing-List: contact dev-help@fineract.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.incubator.apache.org Delivered-To: mailing list dev@fineract.incubator.apache.org Received: (qmail 84831 invoked by uid 99); 7 Jan 2016 18:13:52 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jan 2016 18:13:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 08953C0DD3 for ; Thu, 7 Jan 2016 18:13:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.02 X-Spam-Level: X-Spam-Status: No, score=-0.02 tagged_above=-999 required=6.31 tests=[RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ebXXduikemXn for ; Thu, 7 Jan 2016 18:13:44 +0000 (UTC) Received: from BLU004-OMC2S18.hotmail.com (blu004-omc2s18.hotmail.com [65.55.111.93]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 6A47A42A65 for ; Thu, 7 Jan 2016 18:13:44 +0000 (UTC) Received: from BLU436-SMTP18 ([65.55.111.73]) by BLU004-OMC2S18.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Thu, 7 Jan 2016 10:13:38 -0800 X-TMN: [YKiZRjbCL7TU3kic6ts0AR5AfGs339m/] X-Originating-Email: [markus.geiss@live.de] Message-ID: Subject: Re: Release cycle 2 months, soak period 2 weeks? To: dev@fineract.incubator.apache.org References: From: Markus Geiss Date: Thu, 7 Jan 2016 19:13:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jan 2016 18:13:36.0509 (UTC) FILETIME=[207772D0:01D14977] On 01/07/2016 05:36 PM, Roman Shaposhnik wrote: > On Thu, Jan 7, 2016 at 3:52 AM, Myrle Krantz wrote: >> Hi Fin Fans, >> >> To start the conversation on release cycle, I've documented my suggestion >> here: >> https://cwiki.apache.org/confluence/display/FINERACT/Release+Management >> >> The additions to what was there before consist of: >> * release cycle length added >> * soak period shortened to better match release cycle length > > Would it be possible to spell out your release cadence model more explicitly? > Is it a date-driven cadence (like Ubuntu, lets say) or a feature-driven one? > > Thanks, > Roman. > Given that we are releasing a software product, not a distribution of a certain kind, e.g. Ubuntu, CentOS, Mint, I think a feature-driven model. The development of Fineract will be driven by user requirements, specific to the platform. Bundled libraries will only have influence on the release schedule if a security issue was detected and fixed. Best, Markus .::YAGNI likes a DRY KISS::.