A consolidated update on 4.3.31: what's merged, when it should wrap, where each platform stands, and a request that will get us to a genuinely portable release.
*1. Work merged so far (overall throughput)*
- *Pull requests* merged: *180*
- *Commits*: *317*
- *Line of code*: *+48,299* / −24,478 (including full HTML doc regeneration and code comments)* *- *Line of code **pure C* (.c/.h): *+7,238 / *−1,411
- Active window: 18 Jan 2026 → 24 Aug 2026 (218 days)
- Sustained pace: ≈ 0.83 PR/day, ~25 PRs/month
*2. Remaining for 4.3.31 and ETA*
- Open PRs tagged for 4.3.31: 20
- *As-is *(*20 left*): ~0.8 month →**around mid-September 2026
- If the *backlog doubles* to 40: ~1.6 months → *around mid-October 2026 (more realistic)*
(No fixed due date; pace-derived, assuming the rate holds and PRs are comparable — ~1.8 commits each.)
*3. Platform status*
- From source ✅ working on all Github supported OS.
- apt / Debian ✅ working ✅downstream packagers
- BSD family 3.1. FreeBSD 13.5/14.3/15.0 ✅ working ✅ downstream packagers 3.2. NetBSD 9.2–10.1 ✅ working ⚠️ downstream packagers 3.3. OpenBSD ✅ working ⚠️ downstream packagers
- — RPM / RHEL ✅ working ⚠️ downstream packagers
- — MacOS ⚠️ working with 1 patch⚠️ downstream packagers
...and more work from source (no known issues on any OS).
⚠️ The packaging gap:
*We currently have active downstream packagers for only two systems: Debian and FreeBSD.* RHEL/Fedora (RPM), macOS (Homebrew), and the other BSDs have upstream support, but no established distro maintainer to keep them updated release-to-release. That is the gap we need to close most.
*5. What you can do:* Given how much complexity and customization the build system carries, the most useful thing each of us can do is:
*5.1. **Install Xymon from source* on your preferred system, *run it, and report back*. This will allow us to identify exactly what does not work—whether at configure, build, install, or first run, so it can be fixed for release 4.3.31. Please reply with your platform details and any failures you encounter.
*5.2. Review pull requests (PRs): *- Read the code.
- Understand what it does.
- Test it if it makes sense to do so, and verify that it works.
*5.3. Improve Xymon* *- Just make something* better than it is now; it does not need to be perfect!
- Any code changes need to be reviewed, meaning two people must be involved.
*Thanks *to the *hard work of the Xymon community*, release 4.3.31 is in good shape.
Bruno
*References:*
- Changes: https://github.com/xymon-monitoring/xymon/blob/Changes/Changes
- Release Notes: https://github.com/xymon-monitoring/xymon/blob/Changes/RELEASENOTES
- Terabithia Tracking Migration: https://github.com/xymon-monitoring/xymon/issues/29
- Experimental RPM repository: https://github.com/xymon-monitoring/xymon-rpm
- Experimental RPM file: https://xymon-monitoring.github.io/xymon-rpm/
- Homebrew MacOS https://github.com/xymon-monitoring/homebrew-xymon <https://github.com/xymon-monitoring/homebrew-xymon>