I also agree with a 5.x release.  Forward looking to the latest OS
versions and current security protocols is what needs focused on. If
someone wishes to use an older OS, then the older Xymon version will
work for them.  Backwards compatibility should not be the priority with
this forward facing effort.

Kris Springer
I/O Network Administration


On 3/2/26 9:16 AM, Stef Coene wrote:
> Hi,
>
> I too don't mind dropping support for old distributions but I prefer
> doing this while switching to a 5.x release.
>
> I think most of the old libraries are used on the xymon server and I
> don't see any valid reason to not upgrade the OS to a supported version.
>
> Worst case scenario (like I had when switching from 32-bit to 64-bit)
> you have to export and import the rrd files if you want to keep the
> history graphs.
>
>
> Stef
>
> On 2026-03-01 22:47, Nicola wrote:
>> Hi, I have been thinking about this in a while, and I am now
>> convinced that we should aim at a 4.4.0 release which just drops
>> support for old libraries not available or deprecated in modern
>> OSs/distributions.
>> We can rename and `sed` the version for the current 4.4 branch, but
>> this will ease many of the efforts which are draining our energies to
>> keep compatibility, and at the same time if we need minor bugfixes in
>> the 4.3 branch, we can add them for dinosaurs which still require old
>> libraries.
>> What do you think?
>>
>>
>> Nicola
>> Mastodon <https://joinmastodon.org/>: @nic@mathstodon.xyz
>> <mailto:nic@mathstodon.xyz>
>>
>> _______________________________________________
>> Xymon mailing list -- xymon@xymon.com
>> To unsubscribe send an email to xymon-leave@xymon.com
>
> _______________________________________________
> Xymon mailing list -- xymon@xymon.com
> To unsubscribe send an email to xymon-leave@xymon.com

_______________________________________________
Xymon mailing list -- xymon@xymon.com
To unsubscribe send an email to xymon-leave@xymon.com