For my use, a heartbeat version change would be good enough as long as it includes all the changes made on top of the last release and it is stable.
@bluca, can you please clarify how the versions would be incorrect? I agree whitespace changes should be taken care of Regards, Gaurav On Wed, May 17, 2023 at 8:30 PM John Goetz <j.go...@tecplot.com> wrote: > I made a rough attempt at a PR, bumping the version to 4.4.0 which seemed > a reasonable increment considering the volume of code changes over the past > 2+ years: > > https://github.com/zeromq/libzmq/pull/4550 > > which was promptly closed as "not helpful" by @bluca. Unfortunately, it > looks like he does not read this email list. I'm not sure, but those in > this email thread may want to make another attempt or try to revive my > now-dead PR. > > This is @bluca's (https://github.com/bluca) closing comment: > > "This is not useful. Apart from getting the versions wrong, and apart from > the mess with whitespace changes, dumping git log into NEWS doesn't help, > it needs to be curated. If you want to help, you can do manual QA on > Windows/OSX/QNX/Solaris/BSD* and so on." > > I had asked about the release schedule here and on gitter in January 2023 > which was met with near silence. > > Also, I'm under the impression that the master branch is to be considered > stable, so I'm not sure what he meant by "manual QA". All we're looking for > is a heartbeat version change, right? > - John Goetz > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org https://lists.zeromq.org/mailman/listinfo/zeromq-dev
