I've had a look a the suspendapp jvm shutdown bug ...

# arrow-contributors

[phldavies]

I've had a look a the suspendapp jvm shutdown bug and may have a fix (certainly warrants review) - is it best to push a PR against arrow-kt/suspendapp or arrow-kt/arrow given it's a fairly important fix
i.e. would a 0.5.1 release be worth cutting from arrow-kt/suspendapp

how is versioning of suspendapp going to follow from the merge into arrow-kt/arrow?

[phldavies]

I've raised against arrow-kt/arrow for now: https://github.com/arrow-kt/arrow/pull/3589

[Alejandro Serrano.Mena]

the versioning of SuspendApp will align with the rest of the Arrow libraries from the next release on

[Alejandro Serrano.Mena]

the main arrow repo is the right choice here 🙂

[phldavies]

So this could theoretically push for a 2.0.2 arrow release?

[Alejandro Serrano.Mena]

the plan is to make it 2.1.0, bus yes, a new release

[simon.vergauwen]

Oh, would that also be the case for the newly introduced Ktor modules? That might be dangerous since that puts an immediate "freeze" on binary compatibility. That might be hard to manage.

I think it's okay-ish for SuspendApp, if we figure out this quirk but for the new new stuff like Ktor it might be tricky versioning wise.

[phldavies]

Binary conpatability will be much harder to manage with third party dependencies, i.e. for all integrations. SuspendApp itself is ok depending only on Arrow. The suspendapp-ktor module maybe not so much.