Hi All,
Ken, what's the /Delayed Send/ feature you mentioned? Is it something
like Send Later extension in TB but on the server? How would the clients
use it?
Bron, do you still pursue the goal to close most of the GitHub issues?
Do you have any roadmap for which issues to be closed in the near
future? There are a lot of issues with both 3.0, 3.1 and 3.2 tags (some
even have 2.5 tag), it's not clear which are scheduled to be closed for
which release.
Regards,
Anatoli
*From:* Bron Gondwana <br...@fastmailteam.com>
*Sent:* Monday, July 29, 2019 08:36
*To:* Cyrus Devel <cyrus-devel@lists.andrew.cmu.edu>
*Subject:* Notes 29 July
Present: ellie, Ken, Bron
ellie:
* 3.0.11 release - hopefully tomorrow
* 3.1 checkpoint release?
- Let’s do one now-ish!
- Then we can do another one after the delayed send changes land.
Ken:
* Mailbox by UUID status
- Needs to be rebased.
- Then - need to do some testing! Stand up a new one, replicate over.
* Going to keep working on Delayed Send, including GUID from mailbox record.
Bron:
* Cyruslibs-v26+:
- Need to fix tzdata issue and fixed libicu.
* Calendar Sharing:
- “Shared via JMAP" is clearly bad UI
- Neil and Ken have discussed notifications Inbox and how to deal
with these.
- Have created a task to work on design for the various workflows.
* Handling Calendar scheduling and X-Schedule-User-Address on updates
- A user had issues with a complex mailflow causing participantId to
be null because the schedule address didn't match.
- For now we’ll fix this in the Fastmail middleware for our weird
usecase.
- Need to build a more general way to determine "IsYou" inside Cyrus.
--
Bron Gondwana, CEO, Fastmail Pty Ltd
br...@fastmailteam.com
