Hi Nic,
> Hey, on a related note, I've just noticed that
> "cyrus-imapd/doc/legacy/install-
> upgrade.html" is not up on cyrusimap.org and there doesn't appear to
> be any equivalent. Is there a plan for this?
I'm still bringing it all over into Sphinx. When the legacy docs are
imported into
oli
*From:* Bron Gondwana Via Cyrus-devel
*Sent:* Tuesday, December 27, 2016 21:04
*To:* Cyrus-devel
*Subject:* Re: Release plan blog post
Hi,
Sorry for the delay in responding to this - I left it over Christmas so
I could sit down without distraction and reply when I was back in the
office.
On Sat,
On 12/27/2016 06:04 PM, Bron Gondwana via Cyrus-devel wrote:
Hi,
Sorry for the delay in responding to this - I left it over Christmas
so I could sit down without distraction and reply when I was back in
the office.
On Sat, 24 Dec 2016, at 17:09, Anatoli via Cyrus-devel wrote:
*3. New deploy
Hi,
Sorry for the delay in responding to this - I left it over Christmas
so I could sit down without distraction and reply when I was back in
the office.
On Sat, 24 Dec 2016, at 17:09, Anatoli via Cyrus-devel wrote:
> Hi Bron, all.
>
> Thanks for the update and for the support of the project.
24.12.2016 09:09, Anatoli via Cyrus-devel wrote:
[...]
Once the flush is performed and the lock is applied, a (custom) backup
script could create a snapshot of the partition that would hold the
Cyrus data in a safe-to-backup state. Immediately after creating the
snapshot, the lock would be releas
Hi Bron, all.
Thanks for the update and for the support of the project. That's great
we'll see the 3.0 release soon!
Replying to your last paragraph in the blog post about the community
needs, I believe that what's good for FM is mostly good for the
community too. The FM team is probably the
