-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump supported version #207
Comments
Also to keep in mind that RHEL uses |
I've tried it locally - just pulling the current tip of For Parsec I've tried all those versions as well (though with the latest release, not with the current state). 2.3.2 clearly fails to work (because of a bug that was fixed in 2.3.3). 2.4.0 does work. I'll try using the current tip, see if it still works. |
@ionut-arm It is a little bit inconvenient and it makes things less consistent though not something a user would recognise. |
I know it was a real pain that we support 2.3.3 and RHEL supports 2.3.2 that is something that I have had to deal with. |
Ok, we can keep this open for now with no pending action just yet |
Create `Connection` abstraction for client communication
We're currently targeting version 2.3.3 of the library, with versions 2.4.0 and up probably having an inconsistent API with our abstractions.
There are a couple of options for us to move forward - we can either drop support for 2.3.3 completely and simply continue with 2.4.0, or we can try and keep them both alive as features.
The text was updated successfully, but these errors were encountered: