Return-Path: X-Original-To: apmail-syncope-dev-archive@www.apache.org Delivered-To: apmail-syncope-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6BE5918A5B for ; Wed, 11 Nov 2015 08:12:04 +0000 (UTC) Received: (qmail 71643 invoked by uid 500); 11 Nov 2015 08:12:04 -0000 Delivered-To: apmail-syncope-dev-archive@syncope.apache.org Received: (qmail 71600 invoked by uid 500); 11 Nov 2015 08:12:04 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 71588 invoked by uid 99); 11 Nov 2015 08:12:04 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Nov 2015 08:12:04 +0000 Received: from [192.168.0.7] (rovere.tirasa.net [78.134.5.44]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id AE5BF1A0098 for ; Wed, 11 Nov 2015 08:12:03 +0000 (UTC) To: dev@syncope.apache.org From: =?UTF-8?Q?Francesco_Chicchiricc=c3=b2?= Subject: [DISCUSS] Next release(s) X-Enigmail-Draft-Status: N1110 Message-ID: <5642F84D.3070105@apache.org> Date: Wed, 11 Nov 2015 09:11:57 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Hi all, this discussion is triggered by some request recently received on user@=20 [1] but also about the ongoing development effort towards 2.0.0. AFAICT, the current status can be summarized as follows: 1. feature-wise, core is currently in a quite self-consistent state,=20 even tough relevant new feature are ATM set to be implemented in 2.0.0=20 (mainly SYNCOPE-699 / SYNCOPE-129 / SYNCOPE-534); naturally, there might = be bugs, especially considering the great amount of additions compared=20 to 1.2.X 2. console is still under active development to reach usable state=20 (remember we started it from scratch in 2.0.0) - Fabio and Marco are on i= t 3. enduser is more or less in the same situation of console, possibly=20 a bit more close to the end - Andrea is on it 4. cli should be almost complete - Massimiliano is on it 5. documentation is less than half-way: getting started needs to be=20 adjusted with latest additions and reference guide is simply yet to be=20 written - I am on it, but seeking for contributions, especially by=20 native speakers - read Colm :-) Given this overall situation, I would propose to: (i) keep pushing on 2, 3, 4 and 5 above (ii) fix on (1) on request (iii) as soon as 2 and 3 are in a presentable state, start thinking of = milestone releases (2.0.0-M1, 2.0.0-M2, etc) As far as I can see it, it would be really nice to cut 2.0.0-M1 before=20 the end of year. WDYT? Regards. [1] http://markmail.org/message/ibcz7jx53su73dld --=20 Francesco Chicchiricc=F2 Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/