Upgrade path dio > dio3

[kuhnroyal]

I still think this will be a hard pill to swallow for many projects and not easy to migrate as even in my projects, a lot of 3rd party libraries depend on dio.
I wonder if we can somehow provide a migration package that fuses dio and diox by only changing the backing adapters for a Dio instance. What do you guys think?

[AlexV525]

We have a plan for this. In summary, in the next 6 months, we'll not only publish a new package diox but also maintain a branch in the repo to keep using dio and treat it as a fork.

[AlexV525]

Even though the new project can be used as a fork, it contains breaking changes compared to the previous versions. So make sure changes are addressed in recent usage.

[kuhnroyal]

I am wondering if we should make 4.x branch without breaking changes that we can also release to pub.dev

[AlexV525]

I am wondering if we should make 4.x branch without breaking changes that we can also release to pub.dev

I can't get the point of creating old branches.

[kuhnroyal]

I think it would maybe make it easier to move from dio to diox if there was a path that allows smaller migration steps.

[AlexV525]

if there was a path that allows smaller migration steps.

I would say no from the very start. Changes are already happened and are hard to rebase again.