Xymon Mailing List Archive search

Renaming 4.x-master branch

4 messages in this thread

list Bruno Manzoni · Mon, 19 Jan 2026 18:33:50 +0100 ·

Hi All,

One possible next step could be to rename the 4.x-master branch. Roland pointed out that:

  • “master” isn’t politically correct, especially since the stable branch is named main;

  • “4.x” is ambiguous, as it includes stable 4.3 versions and ties the branch name to a specific major version.

He suggested renaming 4.x-master to devel, unstable, or next (in descending order of preference), which I agree with.

Does anyone have objections or strong preferences before moving forward?

Bruno

list Stef Coene · Mon, 19 Jan 2026 20:57:48 +0100 · 
Hi,

I vote for devel.
Once it's considered usable for endusers, it can be promoted to unstable to iron out the last bugs.

next is more for a complete rewrite from scratch.


Stef
▸ quoted from Bruno Manzoni


On 2026-01-19 18:33, Bruno Manzoni via Xymon wrote:
Hi All,

One possible next step could be to rename the |4.x-master| branch. Roland pointed out that:

  • “master” isn’t politically correct, especially since the stable
    branch is named |main|;

  • “4.x” is ambiguous, as it includes stable 4.3 versions and ties the
    branch name to a specific major version.

He suggested renaming |4.x-master| to *|devel|*, *|unstable|*, or *| next|* (in descending order of preference), which I agree with.

Does anyone have objections or strong preferences before moving forward?

Bruno
list Bruno Manzoni · Tue, 20 Jan 2026 14:03:57 +0100 · 
Hi all

"4.x-master" has been renamed to "devel"

Bruno
▸ quoted from Stef Coene

Le 19.01.2026 à 20:57, Stef Coene a écrit :
Hi,

I vote for devel.
Once it's considered usable for endusers, it can be promoted to 
unstable to iron out the last bugs.

next is more for a complete rewrite from scratch.


Stef


On 2026-01-19 18:33, Bruno Manzoni via Xymon wrote:
Hi All,

One possible next step could be to rename the |4.x-master| branch. 
Roland pointed out that:

  • “master” isn’t politically correct, especially since the stable
    branch is named |main|;

  • “4.x” is ambiguous, as it includes stable 4.3 versions and ties the
    branch name to a specific major version.

He suggested renaming |4.x-master| to *|devel|*, *|unstable|*, or *| 
next|* (in descending order of preference), which I agree with.

Does anyone have objections or strong preferences before moving forward?

Bruno
list Scot Kreienkamp · Tue, 20 Jan 2026 13:42:04 +0000 ·
Bruno, I updated the ruleset to match the devel branch.


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



-----Original Message-----
From: Bruno Manzoni via Xymon <xymon@xymon.com>
Sent: Tuesday, January 20, 2026 8:04 AM
To: xymon@xymon.com
Cc: Bruno Manzoni <user-81df5df13c04@xymon.invalid>
Subject: [Xymon] Re: Renaming 4.x-master branch

Hi all

"4.x-master" has been renamed to "devel"

Bruno

Le 19.01.2026 �� 20:57, Stef Coene a ��crit :
▸ quoted from Bruno Manzoni
> Hi,
>
> I vote for devel.
> Once it's considered usable for endusers, it can be promoted to
> unstable to iron out the last bugs.
>
> next is more for a complete rewrite from scratch.
>
>
> Stef
>
>
> On 2026-01-19 18:33, Bruno Manzoni via Xymon wrote:
>> Hi All,
>>
>> One possible next step could be to rename the |4.x-master| branch.
>> Roland pointed out that:
>>
>>   *
>>
>>     ���master��� isn���t politically correct, especially since the stable
>>     branch is named |main|;
>>
>>   *
>>
>>     ���4.x��� is ambiguous, as it includes stable 4.3 versions and ties the
>>     branch name to a specific major version.
>>
>> He suggested renaming |4.x-master| to *|devel|*, *|unstable|*, or *|
>> next|* (in descending order of preference), which I agree with.
>>
>> Does anyone have objections or strong preferences before moving forward?
>>
>> Bruno
>>
>>
>>
>>
>> To unsubscribe send an email to xymon-leave@xymon.com
>
>
> To unsubscribe send an email to xymon-leave@xymon.com

To unsubscribe send an email to 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.

Attachments (1)