[zeromq-dev] CZMQ "stable" release versioning

Kevin Sapper kevinsapper88 at gmail.com
Mon Apr 25 12:21:35 CEST 2016


Just mark them as you would do for classes `*state* = "*draft*"`. You can
have a look at `api/zframe.c`[1] if you need an example.

[1]
https://github.com/zeromq/czmq/blob/7e4e9202bb1f32c58aef23b7626c280f7e743a95/api/zframe.api#L107

2016-04-25 11:57 GMT+02:00 Osiris Pedroso <opedroso at gmail.com>:

> Pieter,
>
> What is the process of marking an individual method as draft?
> What should one do to have that effect?
>
> Thanks,
> Osiris
>
> Sent from my iPad. Regularly foiled by autocorrect. But duck it..
>
> On Apr 25, 2016, at 04:51, Pieter Hintjens <pieterh at gmail.com> wrote:
>
> Yes, retiring the deprecated APIs and bumping the major version should go
> together.
> On 24 Apr 2016 13:37, "Luca Boccassi" <luca.boccassi at gmail.com> wrote:
>
>> On Sun, 2016-04-24 at 00:09 +0200, Pieter Hintjens wrote:
>> > we can mark individual methods and classes as draft, even within a
>> > stable release.
>> >
>> > On 23 Apr 2016 21:10, "Brian Knox" <bknox at digitalocean.com> wrote:
>> >         When we cut another "stable" release of CZMQ to keep packagers
>> >         happy, I'm wondering what version we'll use - specifically
>> >         around a stable release that include radar/dish,
>> >         scatter/gather and client/server.
>> >
>> >
>> >         I want to start a new version of the rsyslog input and output
>> >         plugins that only support the new thread safe sockets.  To
>> >         avoid ifdef hell in the current plugins I'll probably just
>> >         make new instances - so if the next release is 4, I'll name
>> >         them omczmq4 / imczmq4 etc.
>> >
>> >
>> >         Cheers,
>> >
>> >         Brian
>>
>> Hi,
>>
>> <puts nosy Debian Maintainer hat on>
>>
>> Given since the last release some public APIs have changed in an
>> incompatible way (eg: zmsg_encode/decode signatures), there should be a
>> major version bump (besides an ABI bump), and I'll have to upload a new
>> source/-dev package.
>>
>> A while ago we also talked about the possibility of retiring the
>> deprecated APIs. Is that still on the plate?
>>
>> Kind regards,
>> Luca Boccassi
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
> _______________________________________________
> 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/20160425/c06cf942/attachment.htm>


More information about the zeromq-dev mailing list