Brian, > This issue is the biggest one that we face with both 2.0.7 and 2.0.8. > Would it be possible to back port this fix to both of these branches > as well? But that would mean releasing 2.0.7.1 and 2.0.8.1. I guess > an alternative would be to release a 2.0.9 that branches off 2.0.8 and > has this fix. It would be a huge pain for us if this didn't show up > until 2.1. Do you think this is possible?
Well, here's the release policy: http://www.zeromq.org/docs:policies What it says is "Any change to the API/ABI that breaks old bindings or code is considered a major version change." As introducing new error code does break old code, it should go into 3.0, in short: not anytime soon. I have no idea how to solve the problem. Anyone any experience how it is solved in other projects? Martin _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
