Time for new release

[plumenator]

It looks like several issues were fixed after the last release. Maybe bump the version and publish to crates.io?

[birkenfeld]

Yes, please. The released version doesn't compile with current libc anymore. I'd rather not start and release my own fork.

[kpcyrd]

It's currently not possible to use zmq as dependency with cargo. Can you please publish a new version?

[rotty]

As @erickt noted in PR #97, he'd be willing to share maintainership. Hopefully that works out, and we'll have a new release soonish.

[rotty]

As an update: I'll try to get a few more non-API-breaking changes into master:

• Replace send and recv flags with a more type-safe API #35 (will be addressed later)
• Added rtdealer and fileio3 examples #77
• Fix compilation on different versions of libzmq and cross compilation #93
• Make most socket methods operate on immutable self #104
• PollItems should have a way to get back their sockets #68

After completing this checklist (assuming each item can be handled reasonably quickly), I'll nudge @erickt into publishing a release.

[erickt]

I'd suggest putting #104 off to after this release since it does have some semantic, albeit backwards compatible changes. I'm not sure what are the ultimate implications of having socket methods not require a mutable socket. The rest of the issues seem pretty reasonable.

[rotty]

I'm not entirely sure about #104 yet as well, but quite confident that &self should be OK for our socket wrapper. Anyway, I'll hold off merging it until 0.8 would otherwise be ready from my POV, and we can revisit it then, maybe being a bit wiser. Unfortunatly, I don't know any rust experts that I can bother with this question. Maybe I can bribe^Wconvince someone "authorative" to chime in on this question in the meantime.

[birkenfeld]

You could ask on http://internals.rust-lang.org

[rotty]

The release happened recently, and was uploaded to crates.io. Thanks to all contributors!