Goal: When an event is about to occur show the user a notification. Allow to user to set the time of the alert when creating/editing events. Steps: - Parse alarm data in caldav worker - Pass with occurrence data. - Place in alarm db
(should be blocking+)
Assignee: nobody → jlal
Status: NEW → ASSIGNED
blocking-basecamp: --- → ?
Chris, is this a required feature for v1?
Let me clarify, the work for this is primarily done. (Even prior to feature freeze). The stuff that blocks this is performance related. We should not be landing any feature that negatively impacts performance. The related "blocking" issues are items we need to complete with or without notifications. IMO: I would not use a calendar without notifications.
In triage this was judged to be blocking-basecamp- assuming that the feature these performance issues apply to is not currently active.
blocking-basecamp: ? → -
The performance issues here are related to all sync operations. They are items marked blocking+ for the most part and must be fixed anyway.
If that's the case can you re-nominate with a comment explaining the rationale for why they "must be fixed anyway", and why we would block the release if they weren't, so that people in triage have enough information to make the blocking+ call, otherwise you might have problems landing any patches. Thanks.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Removing requested info flag since already fixed.
Verified on Unagi Build ID: 2012121231070201
You need to log in before you can comment on or make changes to this bug.