migration plan about actix-extras HOT 7 CLOSED

Any user depending directly on the git repo needs to update their link to the new repo.
They'll notice when their builds fail, it's not like we have to semver our git as well.
Just make sure the README.md in the old repo mentions at the headline where these were moved, so they can find out what's the problem fast.

from actix-extras.

Sounds good, I'll set up CI for this repo soonish.

from actix-extras.

It doesn't matter here since the current code isn't published and no one relies on this repository. Actually, we don't include them in the workspace now. Once the new alpha version is released, we should update dependencies and release their new versions.

from actix-extras.

Okay, migration is almost done. The remaining thing is deleting {cors, identity, session} from actix-web repo but I'm cautious because some users may depend on them by pointing to that repo. But indeed we should delete them at some point.

from actix-extras.

thoughts on the setup of this repo and the plan ideas @JohnTitor ?

from actix-extras.

FWIW actix-identiti and actix-session do not compile as latest actix-http and actix-web published to crates.io use time 0.1.42

from actix-extras.

actix-protobuf: migration and archive work are done.

from actix-extras.