Fs2: Release 0.10 final

Created on 6 Jan 2018 · 10Comments · Source: typelevel/fs2

I'd like to get a 0.10 final build out in the next few days if possible. Here's what's left:

https://github.com/functional-streams-for-scala/fs2/issues?q=is%3Aopen+is%3Aissue+milestone%3A0.10

There's also an intermittent test failure in asynchronous resource allocation (6) which only happens on Travis. Next time it happens, I'll open a bug for it with captured output. Is there anything else?

Source

mpilquist

Most helpful comment

@mpilquist I have come with much stable interruption mechanics, I will put PR for that tomorrow. I think you will like it, essentially, everything is resolved in algebra, no more special fby ++ or repeat. Also solves the (6).
So please give me some time to clean this up, because I think this has to go to 0.10

pchlupacek on 6 Jan 2018

🎉4

All 10 comments

pchlupacek on 6 Jan 2018

🎉4

@pchlupacek Wow that's great news! Definitely want to get that in for 0.10. Let me know if there's anything else.

mpilquist on 6 Jan 2018

Also I will enable some issues that I think we shall get in, and if you want pls review them.

pchlupacek on 6 Jan 2018

👍1

@mpilquist @SystemFw where do you think we are with this? I have some other ideas for features to add, but I think we shall release final asap? Any blocking issues? #1063 didn't show up in some time, and not sure what to do about #1071 and #1075

pchlupacek on 28 Jan 2018

I think the http4s people we'll be looking at #1075, which however iiuc should only affect REPL usage.
I also couldn't exactly pinpoint the issue with #1071, although I suspect it's just lack of thread safety in the Java InputStream.

SystemFw on 28 Jan 2018

re #1071 you have tried with RC2? still the same issue ?

pchlupacek on 28 Jan 2018

no, haven't tried yet, will do so today

SystemFw on 28 Jan 2018

I looked in to #1075 and confirmed that it is not a problem with Stream but rather an SBT limitation coupled with a feature we can add to StreamApp later. I'm good with 0.10 final today.

mpilquist on 29 Jan 2018

I think it'd be good to know what's going on in #1071. Whether it is a bug or some expected unobvious behaviour (in which case it'd be good to understand why exactly it behaves this way).