Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
Subject: Re: [DISCUSS] Next release(s)
To: dev@syncope.apache.org
References: <5642F84D.3070105@apache.org> <5642F8A4.1010808@apache.org>
From: andrea <andrea.patricelli@tirasa.net>
Message-ID: <56444965.8060204@tirasa.net>
Date: Thu, 12 Nov 2015 09:10:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5642F8A4.1010808@apache.org>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable


Il 11/11/2015 09:13, Francesco Chicchiricc=F2 ha scritto:
> On 11/11/2015 09:11, Francesco Chicchiricc=F2 wrote:
>> Hi all,
>> this discussion is triggered by some request recently received on=20
>> user@ [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=20
>> 2.0.0 (mainly SYNCOPE-699 / SYNCOPE-129 / SYNCOPE-534); naturally,=20
>> there might be bugs, especially considering the great amount of=20
>> additions compared 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=20
>> on it
>>
>>  3. enduser is more or less in the same situation of console,=20
>> possibly a bit more close to the end - Andrea is on it
>>
On enduser there are two main points to consider:
1. eventual roles and resources management that is considered in user=20
create/update wizard, that can be postponed (or even omitted?).
2. enduser also needs to be "synchronized" with last core developments=20
(on virtual attributes for example).
So is correct to say that is more or less close to the end, but I wanted=20
to underline these two priority issues.
>>  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=20
>> be 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=20
>> of milestone releases (2.0.0-M1, 2.0.0-M2, etc)
>
> Forgot to add:
>
>     (iv) move all residual (and cool) features currently scheduled for=20
> 2.0.0 to 2.1.0
>
>> As far as I can see it, it would be really nice to cut 2.0.0-M1=20
>> before the end of year.
>>
>> WDYT?
>> Regards.
>>
>> [1] http://markmail.org/message/ibcz7jx53su73dld
>
With M1 release I completely agree.
+1

Kind regards,
Andrea