[zeromq-dev] Upcoming stable 2.1 release - devices

MinRK benjaminrk at gmail.com
Mon Mar 14 21:56:48 CET 2011


Re: API-freezing

With 0MQ's unconventional versioning, there are multiple x.y.z
versions before the first stable release (in this case 2.1.3).  I
would not expect
the API-freeze statement to apply to pre-release versions.  For
instance, 2.1.1 introduced new socket types (XPUB/XSUB) and 3 socket
options that were not in 2.1.0, and I think that's fine, because those
were not stable releases.

-MinRK

On Mon, Mar 14, 2011 at 08:07, Ian Barber <ian.barber at gmail.com> wrote:
> On Mon, Mar 14, 2011 at 6:39 AM, Pieter Hintjens <ph at imatix.com> wrote:
>>
>> Lastly, it would be insane to have to make a 2.2 release just to
>> remove these junk programs from the distribution. If our policies
>> force us to do insane things, the policies are broken and need repair.
>
>  +1 to removal of the devices, I don't see the inclusion of the separate
> processes as part of the API - no ones linked programme is going to break
> because of this. Is it perhaps worth including a note in the devices
> directory in case people have old text referencing them, that just points
> the user to zdevices. That could be handy for people that only interact with
> the library via package management.
>
> Ian
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>


More information about the zeromq-dev mailing list