Release candidate: 1.3.0-RC1

Lightmeter Feb 12 2021 Share

Note: a follow-on RC release, RC2, includes a fix for preventing application crash in case of an empty queue msgid. Please use that instead of RC1.

This is an early release of the upcoming Lightmeter Control Center 1.3.0. It provides an opportunity to test the latest changes before the final release scheduled for next week. Please check old issues that affect you and are reported as fixed, as well as any brand new features, and also existing features for regressions.

Changes for testing

  1. News insights: these provide information about updates and critical deliverability news
  2. Prevent logtracker.db growing indefinitely to due to failing to purge temporary data used by Ray Chaser during log processing
  3. Use a pool of read only connections, instead of a single connection shared among many threads, to improve database performance
  4. Detect and support more mail log filenames automatically
  5. Disallow selection of future dates on Observatory date-picker calendar
  6. Update observatory graphs at the same interval as insights (30 seconds_

The full list of merge requests and commits is on GitLab.

How to test

The best way to test this Release Candidate is to use it as you normally use Control Center, in a non-critical environment. Known issues with this release are documented in the README.


Upgrading to an RC release is the same as for any other Control Center release.

Downgrading is also supported, but because downgrading depends upon features which may not yet be stable, successful downgrading should not be relied upon.

Testing specific features

Features which are user-facing can be easily tested using the Web-UI — see the associated GitLab issues for the expected behaviour and screenshots (sometimes) of how they are intended to look.

Where back-end changes affect a particular component (such as Internationalisation, parsing, etc.), deliberately using functionality which depends on those components provides good opportunities to test for regressions.

Reporting issues

Any found issues should be reported to GitLab, clearly stating the version number of the copy of Control Center that you’re using.


Missing your favourite packaging system? Tell us in the comments.

Comments are closed.