Hi there! We’re actively working on releasing the ...

# arrow-contributors

[aballano]

Hi there! We’re actively working on releasing the next arrow version, 0.10.5, that comes with some deprecations, quite a lot of fixes and improvements, before moving to 0.11 and BIO and other interesting features 🙂

So far we’ve merged most of the PRs, only 2 left

Changes in tests + fixes from myself -> https://github.com/arrow-kt/arrow-fx/pull/46/
Deprecate ap from @Jannis -> https://github.com/arrow-kt/arrow-core/pull/40

Please, if you have something in mind that should be added to this release, don’t hesitate on replying on a thread!

[Jannis]

We need to release the arrow-*-test libraries as well! Not all of them are published atm

[aballano]

you mean separately?

[Jannis]

Afaik only arrow-core-test is right now. Also they have lots of duplicated code atm, so not sure if we want to clean that first, but that may take a while because it fails weirdly. I have a pr in fx that does that which fails in weird ways. Basically doesn't find references to stuff from arrow-core-test despite it being included and intellij not showing anything as wrong...

[Jannis]

arrow-fx-test is not published at all for example. Everyone who was testing laws that are now in this module can't build/test with latest snapshot

[aballano]

hmm but afaik we’re not providing anything to devs including the libs, testing-wise, are we? https://github.com/arrow-kt/arrow#about-this-repository

cc @Rachel

[Jannis]

We are providing arrow-core-test and previously arrow-test

[Rachel]

I think the refactor can be done now or afterwards

[simon.vergauwen]

Deprecate CoroutineContext receiver functions in Concurrent and add functions that add CoroutineContext as the first param.

I.e. parMapN(ctx: CoroutineContext, …)

EDIT: add parTupledN as well

[simon.vergauwen]

😬

[Rachel]

However, I can do what Jannis is talking about. The new arrow-XXX-test modules aren't in OSS repository, just arrow-core-test

[Rachel]

And besides that, I would like to change the package because all the arrow-XXX-test modules have the same package and it could generate "problems"

[aballano]

@Rachel @simon.vergauwen if you can create tickets out of those it’ll be perfect for planning, otherwise if you give me a quick reasoning and I can do it myself 🙂

[Rachel]

Good idea, I'm going to create an issue to publish artifacts for all the `arrow-xxx-test`modules and to change the package to differentiate them

[Jannis]

I think the refactor can be done now or afterwards

👍 Don't think it creates any problems. Once they are all published I can give it a test to see if there are any conflicts because of it.

[Rachel]

Thanks @Jannis!! 🙌

[Jorge Castillo]

Is this one ready for a merge @Jannis @aballano? https://github.com/arrow-kt/arrow-core/pull/40#issuecomment-591650925

[aballano]

it is from my side 👍

[Jannis]

That's ready to go. The follow up needs to be done in 0.11

[aballano]

merged