Il giorno 21/gen/2013, alle ore 12.19, Francesco Chicchiriccò ha scritto:

> On 21/01/2013 12:13, Marco Di Sabatino Di Diodoro wrote:
>> On Jan 21, 2013, at 12:11 PM, Fabio Martelli wrote:
>> 
>>> Il giorno 21/gen/2013, alle ore 12.04, Francesco Chicchiriccò ha scritto:
>>> 
>>>> On 21/01/2013 12:00, Fabio Martelli wrote:
>>>>> Il giorno 21/gen/2013, alle ore 11.46, Francesco Chicchiriccò ha scritto:
>>>>> 
>>>>>> Hi all,
>>>>>> following our recent discussion [1], I'd propose to:
>>>>>> 
>>>>>> 1. move SYNCOPE-231 (e.g. CXF migration) and all subtasks to 1.1.0
>>>>>> 2. move SYNCOPE-275 ("Upgrade Spring to 3.2") to 1.1.0 as it requires 
>>>>>> SYNCOPE-231
>>>>>> 3. move SYNCOPE-204 ("Add Karaf features") to 1.2.0
>>>>>> 4. move SYNCOPE-122 ("Password change on an external resource only") to 
>>>>>> 1.2.0
>>>>> I'd keep this lats point to 1.1.0.
>>>>> I think that this important IDM feature shouldn't be delayed.
>>>> I don't see this as straightforward to implement and also quite unrelated 
>>>> to other issues in 1.1.0; from the other side, instead, it sounds close to 
>>>> SYNCOPE-135 ("Password reset") and SYNCOPE-136 ("Password required for 
>>>> resource subscription"), planned for 1.2.0.
>>> I suggest to have SYNCOPE-135 into the 1.1.0 as well.
>>> From my PPOV SYNCOPE-136 is a feature that could be delayed to 1.2.0.
>>> 
>>> I do think that since we are working on an Identity Manager we have to give 
>>> more importance to typical/main idm features.
>>> 
>>> Regards,
>>> F.
>> I propose to move  SYNCOPE-135 and SYNCOPE-136 to the 1.1.0 .
> 
> Ok, let's move everything to 1.1.0 then and plan this release for 2014... :-O
> 
> Jokes apart, I don't think it is of any utility to keep adding features to a 
> release (1.1.0) already containing 109 issues: when will be able to start 
> thinking of releasing 1.1.0 in this way?

it shouldn't change a lot between 109 and 111.
You are right, 109/111 issues are a lot but it's true as well that we are 
talking about the 1.1.0: we already knew that it would be an interesting jump 
onward.

I'd like to suggest something else to be delayed but all the unresolved issues 
currently related to 1.1.0  seem to be important or already in progress (too 
much late to be moved).
I think that SYNCOPE-122 and SYNCOPE-135 will not make the difference in 
reference to the load.

Regards,
F.

> Regards.
> 
>>>>>> If there are no objections, I'll make the necessary changes on JIRA and 
>>>>>> on the roadmap [2]
>>>>>> 
>>>>>> Regards.
>>>>>> 
>>>>>> [1] http://markmail.org/message/5pyfl5auo2qyyyam
>>>>>> [2] https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap
> 
> -- 
> Francesco Chicchiriccò
> 
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/
> 

Reply via email to