384218 - 0.5 Relnote 'other issues' not quite right on CalDAV items

Status: VERIFIED FIXED

(Calendar :: Website, defect)

Description

[Bruno Browning]

Some relatively minor concerns about the CalDAV issues raised on this page:

1. "Concurrent editing of ICS & CalDAV calendars by multiple users can lose data (bug 329570)"
* We now do etag checking on CalDAV to check for changed data before modify/delete. The etag checking is not beyond improvement, but solid enough for most use. I guess I'd suggest removing the CalDAV reference here instead of trying to explain that concurrent editing of ICS is dangerous but that CalDAV is only likely to fail if you really try to make it.

2. "Unifinder and task view are empty when using a CalDAV calendar"
* as noted in the bug, Sebo was later unable to reproduce this; I certainly haven't seen anything like it for months barring an offline server or incorrect URL. I wonder if the intent here was not to relnote bug 365641 instead, which is somewhat similar and does still seem to recur.

3. "Automatic reloading and and/or refreshing and reloading is not possible on CalDAV calendars. This issue is more severe on the BedeWork CalDav server than on Cosmo" 
* The second sentence here makes no sense to me. We don't reload/refresh at all, period, regardless of server. Suggest we lose that second sentence.

Comment 1

[Simon Paquet [:sipaq]]

Hi Bruno,
thanks for your comments.

(In reply to comment #0)
> 1. "Concurrent editing of ICS & CalDAV calendars by multiple users can lose
> data (bug 329570)"
> * We now do etag checking on CalDAV to check for changed data before
> modify/delete. The etag checking is not beyond improvement, but solid enough
> for most use. I guess I'd suggest removing the CalDAV reference here instead 
> of trying to explain that concurrent editing of ICS is dangerous but that 
> CalDAV is only likely to fail if you really try to make it.

I changed this to "Concurrent editing of remote calendars by multiple users can lose data".

> 2. "Unifinder and task view are empty when using a CalDAV calendar"
> * as noted in the bug, Sebo was later unable to reproduce this; I certainly
> haven't seen anything like it for months barring an offline server or 
> incorrect URL. I wonder if the intent here was not to relnote bug 365641 
> instead, which is somewhat similar and does still seem to recur.

What is your recommendation here? Remove the relnote for bug bug 356021 and relnote bug 365641 instead? The intention of this comment is a little bit unclear to me.

> 3. "Automatic reloading and and/or refreshing and reloading is not possible 
> on CalDAV calendars. This issue is more severe on the BedeWork CalDav server 
> than on Cosmo"
> * The second sentence here makes no sense to me. We don't reload/refresh at
> all, period, regardless of server. Suggest we lose that second sentence.

Done.

Leaving bug to open to address part 2 of comment 0 and comment 1.

Comment 2

[Bruno Browning]

Sorry to be unclear on that second item: I was rather hoping that  whoever added the 'relnote' keyword to bug 356021 would chime in. For my part, I'd relnote 365641 instead of 356021.

Comment 3

[Simon Paquet [:sipaq]]

Fix checked in.