We need a backwards-incompatible release because of this change (which I absolutely like though!).
Context: I'm updating a bunch of crates from e-io 0.3 and 0.4 to 0.5 and their release is imminent. But given the upcoming breaking change in eio - if I can rebase my work on top of a freshly-released 0.6 that would be ideal. Otherwise, I need to do - relatively soon - another backwards incompatible release of these crates.
Is there any additional scope we need so as to branch a new release or shall we just do it now?
We need a backwards-incompatible release because of this change (which I absolutely like though!).
Context: I'm updating a bunch of crates from e-io 0.3 and 0.4 to 0.5 and their release is imminent. But given the upcoming breaking change in eio - if I can rebase my work on top of a freshly-released 0.6 that would be ideal. Otherwise, I need to do - relatively soon - another backwards incompatible release of these crates.
Is there any additional scope we need so as to branch a new release or shall we just do it now?