cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: Cocoon 2.1.6 Release Plan, Re: Syncing 2.1.x and 2.2
Date Tue, 19 Oct 2004 15:40:41 GMT
Unico Hommes wrote:
> Vadim Gritsenko wrote:
> 
>> Carsten Ziegeler wrote:
>>
>>> According to the wiki we still have some open blocks/areas.
>>>
>>>> http://wiki.apache.org/cocoon/MergingBranches
>>>
>>>
>>> In addition it seems that some new things have been checked in
>>> only to one branch, either trunk or 2.1.x, but not to both.
>>> Could everyone please verify that all patches, fixes etc. are
>>> applied accordingly? Of course, there are features that
>>> should only apply to 2.2.
>>>
>>> I see a successful merging as a minimum requirement for the 2.1.6
>>> release.
>>
>>
>> What else beside merging? I'd say checking out all tests and samples 
>> is another required step. Going through TODO/Bugzilla items to 
>> identify blockers could be the third thing. I'm aware of at least one 
>> open issue [1] which could be addressed in 2.1.6
>>
>> Vadim
>>
>> [1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=109596886721684
> 
> 
> Both the test and the code seem to be wrong. IIUC the behavior should be 
> that failing to redirect from flow should raise a ProcessingException. 
> IOW a 500 response status code should be the correct behavior. However 
> the test case tests for a 404 and the actual response code seems to be 200.

Done. More issues which must be fixed before 2.1.6: Failing reader mime-type 
anteater tests.

Vadim

Mime
View raw message