libical 2.0.0 release checklist

[Ken Murchison]

I will look into it


--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University

> On Aug 17, 2015, at 6:25 PM, Allen Winter <winter at kde.org> wrote:
> 
>> On Monday, August 17, 2015 12:58:24 PM Ken Murchison wrote:
>> After reading RFC 5545 again (section 3.3.11) I think the clients are to 
>> blame for some of this.  It appears that commas are always supposed to 
>> be escaped in TEXT values, unless the comma is splitting multiple 
>> values.  Apple clearly isn't doing this in their X- property.
>> 
>> I'm thinking we should be liberal in what we except, meaning that for a 
>> known single value property, we should accept both escaped and 
>> un-escaped commas. In the case of a multi-valued property like 
>> CATEGORIES, we should split on any un-escaped comma.  When outputting 
>> iCalendar data we should follow the spec.
> I agree.
> Will you work on this?
> 
> 
>> 
>>> On 08/17/2015 11:31 AM, Kent Sutherland wrote:
>>> The reason for the exception to X-APPLE-STRUCTURED-LOCATION is because Apple isn't escaping commas in the property value. It looks like that could be related to #79 if RESOURCE shouldn't have escaped commas either, I didn't realize there were similar issues on other properties.
>>> 
>>> Kent
>>> 
>>>> On Aug 17, 2015, at 11:27 AM, Ken Murchison <murch at andrew.cmu.edu> wrote:
>>>> 
>>>> 
>>>>> On 08/17/2015 11:16 AM, Allen Winter wrote:
>>>>> Howdy,
>>>>> 
>>>>> Here is my checklist for the 2.0.0 release:
>>>>> * fix escaping commas in a CATEGORY (issue#77)
>>>>> * fix escaping commas in a RESOURCE (issue#79)
>>>> I was going to look into the whole multi-valued properties and comma stuff, hopefully soon.  It appears to be a mess.  I was actually thinking that maybe we could add a multi-valued flag to the design data, but that might be too big of a bite for this.
>>>> 
>>>> I am wondering why we assume that an X- property can be multi-valued and therefore we have to make an exception for X-APPLE-STRUCTURED-LOCATION.  It would seem to me that we should treat any X- property as a an opaque value.
>>>> 
>>>>> * should we handle invalid characters in parameters nicely? (issue#121)
>>>> Should we look at RFC 6638?
>>>> 
>>>> 
>>>>> Anything else?
>>>>> 
>>>>> I really want to get this thing released.  any and all help with the above appreciated.
>>>>> 
>>>>> -Allen
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> libical-devel mailing list
>>>>> libical-devel at lists.infradead.org
>>>>> http://lists.infradead.org/mailman/listinfo/libical-devel
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> libical-devel mailing list
>>>> libical-devel at lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/libical-devel
>>> 
>>> _______________________________________________
>>> libical-devel mailing list
>>> libical-devel at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/libical-devel
>