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 (734) 384-6403 | 1-734-915-1444 | Scot.Kreienkamp@la-z-boy.com One La-Z-Boy Drive | Monroe, Michigan 48162 | la-z-boy.com<http://www.la-z-boy.com/> facebook.com/lazboy<http://facebook.com/lazboy> | instagram.com/lazboy<https://instagram.com/lazboy> | youtube.com/lazboy<http://youtube.com/lazboy>
[cid:lazboy_2024_inc_navy_4a4d68ec-613a-4141-a2aa-d73a2ae749f6.png] From: Nicola <canne74@gmail.com> Sent: Thursday, January 15, 2026 12:44 PM To: Xymon mailinglist <xymon@xymon.com> Cc: Bruno Manzoni <bruno.manzoni@ubi-network.ch> Subject: [Xymon] Re: Project direction and next steps - feedback requested
You don't often get email from canne74@gmail.com<mailto:canne74@gmail.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
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-mirrortoxymon - 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
Nicola Mastodon<https://joinmastodon.org/>: @nic@mathstodon.xyz<mailto:nic@mathstodon.xyz>
Il giorno gio 15 gen 2026 alle ore 06:47 Bruno Manzoni via Xymon <xymon@xymon.com<mailto: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
Xymon mailing list -- xymon@xymon.com<mailto:xymon@xymon.com> To unsubscribe send an email to xymon-leave@xymon.com<mailto:xymon-leave@xymon.com>
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
