[zeromq-dev] ZeroMQ 4.2 release, planning
Kevin Sapper
kevinsapper88 at gmail.com
Wed Nov 2 14:26:04 CET 2016
In general czmq and zyre are stable on master. Cutting releases IMO
makes only sense to push API changes, i.e.
draft->stable->deprecated->removed.
On Mi, Nov 2, 2016 at 2:08 , Wes Young <wes at barely3am.com> wrote:
> +1
>
> with the pace czmq and zyre are beginning to move at, unless we start
> cutting releases every few weeks/months we’re probably using this
> methodology for a bit while things evolve and settle.. [which is OK,
> should make it easier to actually cut releases if anything]
>
> it’d be nice to have something more stable to regularly point to,
> but i don’t think we’re there yet.. (i pretty much cut pyzyre to
> work like this when it builds the czmq bindings[1], just updating the
> commits and sha1’s, which is a little more manual, but keeps things
> chugging along).
>
> [1]
> https://github.com/wesyoung/pyzyre/blob/master/buildutils/czmq/fetch.py#L33
>
>> On Nov 1, 2016, at 7:52 PM, Brian Knox <bknox at digitalocean.com>
>> wrote:
>>
>> No objections here - been using czmq off various commits off head
>> for over a year anyway
>
> --
> wes
> wesyoung.me
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20161102/97d802a7/attachment.htm>
More information about the zeromq-dev
mailing list