On Sun, September 16, 2018 07:29, Bron Gondwana wrote: > On Sat, Sep 15, 2018, at 00:20, Samir Aguiar wrote: > >> Hi Bron, >> >> >> On 09/12/2018 03:49 AM, Bron Gondwana wrote: >> >>> Samir: what's your plan for moving those users to something which >>> supports standard ? Because the downside of keeping on supporting a legacy >>> ANNOTATEMORE in Cyrus is that somebody has to >>> maintain that forever if you're never planning to get off it, either you or >>> everyone >>> else touching that code! >> >> Yes, that's a fair point. >> >> >> The plan is to update our client to use METADATA instead of >> ANNOTATEMORE, while keeping support for both in the server. After this >> we deprecate ANNOTATEMORE to signal customers that they should upgrade their >> clients. >> This deprecation should happen mostly likely within two >> years, and in the next years we will be removing it completely from the >> server. > > Right! OK, we'll add it back in 3.0 and 3.2 then (with a config option to > turn it on), > and deprecate it after that :) > > I have CC'd ellie who is making the releases and created > https://github.com/cyrusimap/cyrus-imapd/issues/2525
Thanks. I also need ANNOTATEMORE and METADATA active at the same time. Updating to 3.X would otherwise be impossible. I suspect there are others, perhaps not on this list, with the same needs.
