Status of 2.x stream

[nedtwigg]

Hello! Thanks very much for maintaining this great library! The changes coming in 2.x seem good, I'm eager to be an early adopter of it.

Do you have rough ideas around

• what might be broken in the 2.x train
• what might still change in the 2.x train
• how long until the 2.x train is out of beta

Not looking for hard commitments or anything, just your general vibe.

[bitwiseman]

There was extensive discussion on the first 2.0 alpha: #1938

There are requests to make larger breaking changes, mainly around exception throwing/streaming support... Concrete follow up contributions haven't materialized yet.

I'll look at other filed issues and try to give you a more concrete answer.

[nedtwigg]

Amazing, thanks for the link to that discussion, I didn't see it when I searched the issues.

Am I correct that the 2.x train is expected to have the same defect rate as 1.x? So the alpha status is more about API feedback rather than "we're not sure if this works"?

[gsmet]

Hey @bitwiseman ,

There are requests to make larger breaking changes, mainly around exception throwing/streaming support... Concrete follow up contributions haven't materialized yet.

From our discussions, the subject of exceptions was closed for 2.x so I didn't make it a high priority on my side.

Your plan of having a small 2.x with some cleanups makes perfect sense, it's already a nice improvement.

HTH.

[bitwiseman]

@nedtwigg

Am I correct that the 2.x train is expected to have the same defect rate as 1.x? So the alpha status is more about API feedback rather than "we're not sure if this works"?

Yes. It is only alpha because I'm taking this window of releases as potentially adding more API breaking changes. All releases still have the same level of testing and expected functional stability.

[bitwiseman]

@gsmet
Ah, okay. I thought you had other potential ideas for API updates for this release. Thanks!