Message from @David
I'm currently trying to track down a reasonably large memory leak in the MercuryB module;
I also have to complete porting the web-based Mercury licensing system to the new
MercuryB interface (that process is nearly finished). Even though a lot of users don't use
the MercuryB module (something I hope will change with the new static site support), I
really can't release a version of Mercury when there's a fairly important outstanding issue
in any of the modules.
Once I've tracked the memory leak, there will be a short beta period (basically just a week,
to make sure I haven't overlooked anything obvious) - it doesn't need to be longer than that
because the new Mercury has been running flawlessly on Demeter, my new web presence
system, for nearly two months now, including the DKIM support and the static site
serving in MercuryB. After that, I'll be getting it out the door as quickly as I possibly can.
In case you're interested, the ACME support I mentioned in my post earlier this year is
now also working, and Mercury on Demeter is automatically obtaining and renewing
certificates from LetsEncrypt (not just for the MercuryB module, but for all the SSL-capable
modules on the system).
I've been rather hampered in work recently by a fairly severe bout of RSI in my right arm,
but that's gradually coming right. It's meant I've only been able to work an hour or two
at a time before the pain gets too intense, and that's slowed me down a lot.
Sorry for all the delays - nothing ever seems to be easy any more, and I should really
learn not to make release estimates, because I never seem to be able to get them right
(except this time, of course <grin>.)
Cheers!
-- David --
Message from @David
I'm currently trying to track down a reasonably large memory leak in the MercuryB module;
I also have to complete porting the web-based Mercury licensing system to the new
MercuryB interface (that process is nearly finished). Even though a lot of users don't use
the MercuryB module (something I hope will change with the new static site support), I
really can't release a version of Mercury when there's a fairly important outstanding issue
in any of the modules.
Once I've tracked the memory leak, there will be a short beta period (basically just a week,
to make sure I haven't overlooked anything obvious) - it doesn't need to be longer than that
because the new Mercury has been running flawlessly on Demeter, my new web presence
system, for nearly two months now, including the DKIM support and the static site
serving in MercuryB. After that, I'll be getting it out the door as quickly as I possibly can.
In case you're interested, the ACME support I mentioned in my post earlier this year is
now also working, and Mercury on Demeter is automatically obtaining and renewing
certificates from LetsEncrypt (not just for the MercuryB module, but for all the SSL-capable
modules on the system).
I've been rather hampered in work recently by a fairly severe bout of RSI in my right arm,
but that's gradually coming right. It's meant I've only been able to work an hour or two
at a time before the pain gets too intense, and that's slowed me down a lot.
Sorry for all the delays - nothing ever seems to be easy any more, and I should really
learn not to make release estimates, because I never seem to be able to get them right
(except this time, of course <grin>.)
Cheers!
-- David --
