Xymon Mailing List Archive search

Project direction and next steps - feedback requested

list Scot Kreienkamp
Thu, 15 Jan 2026 18:36:10 +0000
Message-Id: <user-77c5bd725399@xymon.invalid>

I have experience with Github actions for other reasons… I could probably figure out the tags.  It would be great if it could automatically build the RPMs, tarballs, debs, or whatever other packaging is necessary on each release so there’s a real pipeline.  I don’t have experience with building packages though. 



Scot Kreienkamp | Applications Infrastructure Architect | La-Z-Boy Corporate 
(XXX) XXX-XXXX | X-XXX-XXX-XXXX | user-9678697f1438@xymon.invalid
One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com
facebook.com/lazboy  | instagram.com/lazboy | youtube.com/lazboy


From: Nicola <user-2c63804b6921@xymon.invalid>
Sent: Thursday, January 15, 2026 12:44 PM
To: Xymon mailinglist <xymon@xymon.com>
Cc: Bruno Manzoni <user-81df5df13c04@xymon.invalid>
Subject: [Xymon] Re: Project direction and next steps - feedback requested


Hi, I am willing to help (unfortunately my C skills are at the "hello world" level, from university studies).

My votes:

* rename (or duplicate) `xymon-svn-mirror` to `xymon`

* link the Xymon website to the new repo, instead of SVN/SourceForge

* incorporate the pending patches and publish a 4.3.31 (or maybe 4.3.32, since there's already a branch for .31) version, so we can also measure the interest

* enable github actions if anyone has experience to publish releases when a new tag is submitted

* either backport the needful from 4.4alpha or start testing fixes in there




Il giorno gio 15 gen 2026 alle ore 06:47 Bruno Manzoni via Xymon <xymon@xymon.com> ha scritto:

Hi all,

Quick follow-up.

So far, there seems to be agreement that:

· 4.3 is the current production version.

· 4.4 is unfinished and experimental.

· The main blocker is the lack of a shared Git workflow.

To move forward, feedback is needed, and input from everyone is welcome.
Feedback from long-time maintainers and contributors would be especially appreciated (JC Cleaver in particular; Henrik Storner is already involved).

In short:

· Who is willing to help?

· Is https://github.com/xymon-monitoring/xymon-svn-mirror a good place to move forward?

· If not, is there a better proposal (for example under https://github.com/xymon-monitoring)?

· What should be the next concrete step?

Short replies are perfectly fine.

Thanks,
runo