Proc

I don't think you want me to release v5 in the current state (not if I'm taking semver v5 serious). First of all #380 and #381 are things we'll want...

@parasyte if you want to do that and test it on all systems I'd be open for that.

> This means that we can't effectively lock the notify dependency to a specific pre-release Ok that is actually bad and I didn't know of that, as I was always...

Ok so as I won't be having as much time to bring it into the shape as I'd like to, my current option is only to: A) Postpone this further...

The biggest breaking change is that there is no debouncer. I could hack one up in the next two weeks and we'll ship with that, making a migration at least...

v4 did, so the problem are people coming from v4 waiting for a stable v5

@samuelcolvin thanks Things to do definitely for v5: - [x] Upgrade path from v4 - [x] Overhaul documentation to reflect current state - [x] List of changes - [x] Remove...

The upcoming 5.0.0-pre.16 is the final RC. Please test this out. If no further issues arise I'll do a 5.0 stable release in two weeks.

With that said it is probably also time for new maintainers. My own use case for this crate was ~3 years ago, and I think somebody invested would fit that...

5.0.0-pre.16 is out