[zeromq-dev] [zeromq-announce] When is new version of libzmq getting released?

[Gaurav Gupta]

Hi Team,

Just checking again when the new version is going to be released.

Someone tried to bump the version to R4.4.0 ( https://github.com/zeromq
/libzmq/pull/4550 ) but the issue was closed before changes could be merged.

Kindly confirm

Regards,
Gaurav

On Tue, May 16, 2023 at 10:54 PM Francesco <francesco.montorsi at gmail.com>
wrote:

> Hi all,
> Let me add myself (and actually the company I work for) as a +1 voters for
> a new release.
> We're using libzmq in production since several years and we're rebuilding
> it in our CI/CD from a specific master version of ~1yr ago. Still having a
> version 4.3.5 would be really good to clearly mark the point in time and
> communicate everyone that...well...the project is not dead! :)
>
> If some help is needed to get the release done I think I can volunteer to
> help...
>
> Thanks,
>
> Francesco
>
>
>
> Il lun 15 mag 2023, 17:09 Bill Torpey <wallstprog at gmail.com> ha scritto:
>
>> Hi All:
>>
>> FWIW, in my shop procedures to release code into prod are very strict,
>> and versioning is a key part of that.  A single release consists of a dozen
>> or so component packages — some of these are open-source project hosted by
>> others  (e.g., https://github.com/zeromq/libzmq
>> <https://github.com/nyfix/libzmq>), some are open-source projects that
>> we host ourselves (e.g., https://github.com/nyfix/OZ), and some are
>> internal closed-source projects.
>>
>> In order to build the open-source components, both our own and others’,
>> we need to create a “parent” project that provides the required tooling,
>> boilerplate, etc.  for our internal build process, and then pull in the
>> open-source “core” (e.g., using git submodules).  For open-source projects
>> that we don’t host ourselves, the submodule points to a fork that can
>> contain commits that are essential to us, but for one reason or another
>> have not (yet) been accepted upstream.
>>
>> As you can imagine, this is all a major PITA. Anything that makes this
>> process easier to track and audit is helpful.
>>
>> I’ll also add that not having defined releases is a major impediment to
>> incorporating ZeroMQ (or any other project) in a typical corporate
>> environment.
>>
>> Regards,
>>
>> Bill
>>
>>
>> On May 15, 2023, at 10:34 AM, Gaurav Gupta <eng.gupta26 at gmail.com> wrote:
>>
>> Thanks to all for sharing their inputs.
>>
>> I would agree that it's time to create a new version. And 320 commits is
>> not a small number, even if there is no significant feature in those 320
>> commits.
>>
>> Would request the team to please release a new version
>>
>> Regards,
>> Gaurav
>>
>> On Mon, May 15, 2023 at 8:03 PM Matthias Gabriel <
>> matthias.gabriel at etit.tu-chemnitz.de> wrote:
>>
>>> Sorry, there was a typo:
>>>
>>> Maybe it helps turning the question around: what keeps us from releasinf
>>> the next version (point release). If nobody has a good argument then it's
>>> time, I'd say :)
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20230523/330f47e4/attachment.htm>