Discussion:
[zeromq-dev] CZMQ old v2 API proposal: deprecated -> retired
Luca Boccassi
2016-10-28 17:56:40 UTC
Permalink
Hello all,

Since we are hopefully close to release libzmq 4.2, I checked what's the
API/ABI status in CZMQ master vs 3.0.2. There are a _lot_ of ABI
breakages, and a couple of API too.

Given it's been now 2 years and 2 weeks since 3.0.0 was released and the
v2 APIs were declared DEPRECATED
( https://github.com/zeromq/czmq#toc3-8224 ), I hereby propose to
declare them RETIRED as per C4.1 process and remove them from the
repository.

I thought it would have been nice to do a bugfix release first, but
API/ABI is already broken and it would be too much pain to revert all
those changes and then put them back on.

This way we bump to major version 4.0.0 and break ABI all in one fell
swoop, and minimise disruption.

Comments, objections?

Kind regards,
Luca Boccassi
Wes Young
2016-10-28 18:09:38 UTC
Permalink
fwiw; what’s currently in czmq master *appears* to work OK with zmq-4.1-, i wanna say i have even tested it against zmq-4.2 (libzmq-master) w/o much issue, both not *extensively*, but enough to have some confidence in it.

so 
 +1 for pushing it further faster [if that means anything anyway].
Post by Luca Boccassi
Comments, objections?
--
wes
wesyoung.me
Patrik VV.
2016-10-29 13:30:29 UTC
Permalink
I love this proposal! 😍
Post by Luca Boccassi
Hello all,
Since we are hopefully close to release libzmq 4.2, I checked what's the
API/ABI status in CZMQ master vs 3.0.2. There are a _lot_ of ABI
breakages, and a couple of API too.
Given it's been now 2 years and 2 weeks since 3.0.0 was released and the
v2 APIs were declared DEPRECATED
( https://github.com/zeromq/czmq#toc3-8224 ), I hereby propose to
declare them RETIRED as per C4.1 process and remove them from the
repository.
I thought it would have been nice to do a bugfix release first, but
API/ABI is already broken and it would be too much pain to revert all
those changes and then put them back on.
This way we bump to major version 4.0.0 and break ABI all in one fell
swoop, and minimise disruption.
Comments, objections?
Kind regards,
Luca Boccassi
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Doron Somech
2016-10-30 08:07:03 UTC
Permalink
Seems like a good idea.
Post by Patrik VV.
I love this proposal! 😍
Post by Luca Boccassi
Hello all,
Since we are hopefully close to release libzmq 4.2, I checked what's the
API/ABI status in CZMQ master vs 3.0.2. There are a _lot_ of ABI
breakages, and a couple of API too.
Given it's been now 2 years and 2 weeks since 3.0.0 was released and the
v2 APIs were declared DEPRECATED
( https://github.com/zeromq/czmq#toc3-8224 ), I hereby propose to
declare them RETIRED as per C4.1 process and remove them from the
repository.
I thought it would have been nice to do a bugfix release first, but
API/ABI is already broken and it would be too much pain to revert all
those changes and then put them back on.
This way we bump to major version 4.0.0 and break ABI all in one fell
swoop, and minimise disruption.
Comments, objections?
Kind regards,
Luca Boccassi
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Kevin Sapper
2016-10-31 06:56:48 UTC
Permalink
Let's do it!
Post by Doron Somech
Seems like a good idea.
I love this proposal! 😍
Post by Luca Boccassi
Hello all,
Since we are hopefully close to release libzmq 4.2, I checked what's the
API/ABI status in CZMQ master vs 3.0.2. There are a _lot_ of ABI
breakages, and a couple of API too.
Given it's been now 2 years and 2 weeks since 3.0.0 was released and the
v2 APIs were declared DEPRECATED
( https://github.com/zeromq/czmq#toc3-8224 ), I hereby propose to
declare them RETIRED as per C4.1 process and remove them from the
repository.
I thought it would have been nice to do a bugfix release first, but
API/ABI is already broken and it would be too much pain to revert all
those changes and then put them back on.
This way we bump to major version 4.0.0 and break ABI all in one fell
swoop, and minimise disruption.
Comments, objections?
Kind regards,
Luca Boccassi
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________
zeromq-dev mailing list
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Loading...