Unifying Windows and Linux Releases

[gujiaweijoe <gu...@foxmail.com>]

Hi all,

As Calvin mentioned, BifroMQ currently provides two types of releases: Windows and Linux. In practice, however, the only difference between them lies in the scripts under the bin directory, while the core artifacts are identical.
Given this, I’d like to start a discussion on whether we should merge the two into a single unified release.

Pros:
Cleaner release structure and easier maintenance
Avoids duplication, since the core outputs are the same

Cons:
May cause some initial confusion for users
Additional documentation or clarification may be needed

I’d appreciate any insights, concerns, or suggestions from the community.


Best regards,
Gu Jiawei (gujiaweijoe)

Re: Unifying Windows and Linux Releases

[Christofer Dutz <ch...@c-ware.de>]

+1, as it reduces the number of artifacts needing review during a release.

Chris

Gesendet von Outlook für Android<https://aka.ms/AAb9ysg>
________________________________
From: Yonny Hao <po...@gmail.com>
Sent: Friday, January 23, 2026 4:20:21 AM
To: dev@bifromq.apache.org <de...@bifromq.apache.org>
Subject: Re: Unifying Windows and Linux Releases

Hi Jiawei,

Thanks for bringing this up.

The separation of Windows and Linux binary packages is largely historical,
dating back to before BifroMQ joined the Incubator. As you noted, the only
real difference today is in the startup scripts, while the core artifacts
are identical.

I agree that merging them into a single unified binary package in future
releases would make sense. It would reduce user confusion and also simplify
the release and voting process by avoiding unnecessary duplication.


Best,

On Wed, Jan 21, 2026 at 10:33 PM gujiaweijoe <gu...@foxmail.com>
wrote:

> Hi all,
>
> As Calvin mentioned, BifroMQ currently provides two types of releases:
> Windows and Linux. In practice, however, the only difference between them
> lies in the scripts under the bin directory, while the core artifacts are
> identical.
> Given this, I’d like to start a discussion on whether we should merge the
> two into a single unified release.
>
> Pros:
> Cleaner release structure and easier maintenance
> Avoids duplication, since the core outputs are the same
>
> Cons:
> May cause some initial confusion for users
> Additional documentation or clarification may be needed
>
> I’d appreciate any insights, concerns, or suggestions from the community.
>
>
> Best regards,
> Gu Jiawei (gujiaweijoe)
>
>

--
Yonny(Yu) Hao

Re: Unifying Windows and Linux Releases

[Yonny Hao <po...@gmail.com>]

Hi Jiawei,

Thanks for bringing this up.

The separation of Windows and Linux binary packages is largely historical,
dating back to before BifroMQ joined the Incubator. As you noted, the only
real difference today is in the startup scripts, while the core artifacts
are identical.

I agree that merging them into a single unified binary package in future
releases would make sense. It would reduce user confusion and also simplify
the release and voting process by avoiding unnecessary duplication.


Best,

On Wed, Jan 21, 2026 at 10:33 PM gujiaweijoe <gu...@foxmail.com>
wrote:

> Hi all,
>
> As Calvin mentioned, BifroMQ currently provides two types of releases:
> Windows and Linux. In practice, however, the only difference between them
> lies in the scripts under the bin directory, while the core artifacts are
> identical.
> Given this, I’d like to start a discussion on whether we should merge the
> two into a single unified release.
>
> Pros:
> Cleaner release structure and easier maintenance
> Avoids duplication, since the core outputs are the same
>
> Cons:
> May cause some initial confusion for users
> Additional documentation or clarification may be needed
>
> I’d appreciate any insights, concerns, or suggestions from the community.
>
>
> Best regards,
> Gu Jiawei (gujiaweijoe)
>
>

-- 
Yonny(Yu) Hao