<!DOCTYPE html><html><head><title></title><style type="text/css">
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style="font-family:Arial;">On Tue, Nov 5, 2019, at 12:04, Ricardo Signes wrote:<br></div><blockquote type="cite" id="qt"><div>So, I think the plan was to cut a stable Cyrus 3.2 after we had stable JMAP. Is that time now? We talked about this on the Zoom call today.<br></div></blockquote><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">I think we're pretty close to it. The big question is: do we fork what will eventually become 3.2 and keep stabilising on it while we ship UUID mailboxes on master, or do we finish 3.2 before we merge uuid mailboxes.<br></div><div style="font-family:Arial;"><br></div><blockquote type="cite" id="qt"><div>Cyrus master has pretty stable for JMAP core and mail. I think we need to do one more pass through to look for places where Cyrus extensions might leak through without the correct `using` options, but apart from that, I don't think we expect its mail API to change apart from bugfixes.<br></div></blockquote><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Yep, legit. The one big thing still missing there is PushSubscriptions. I'd be keen to finish writing that. I mean:<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;"><a href="https://github.com/cyrusimap/cyrus-imapd/issues?q=is%3Aopen+is%3Aissue+label%3A3.2">https://github.com/cyrusimap/cyrus-imapd/issues?q=is%3Aopen+is%3Aissue+label%3A3.2</a><br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">We should probably do a push and resolve all of those, then boom let's go.<br></div><div style="font-family:Arial;"><br></div><blockquote type="cite" id="qt"><div>The other part of the conversation was declaring pre-3 releases EOL except for security fixes.<br></div><div><br></div><div>I don't have much of a horse in this race, but it felt like a bit of looming question.<br></div></blockquote><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Generally the pattern has been "current stable and oldstable are supported" - so that would be 3.2 and 3.0 once we release 3.2. I'm good with that.<br></div><div style="font-family:Arial;"><br>Bron.<br></div><div style="font-family:Arial;"><br></div><div id="sig56629417"><div class="signature">--<br></div><div class="signature"> Bron Gondwana, CEO, Fastmail Pty Ltd<br></div><div class="signature"> brong@fastmailteam.com<br></div><div class="signature"><br></div></div><div style="font-family:Arial;"><br></div></body></html>