Skip to content

Latest commit

 

History

History
25 lines (15 loc) · 1.55 KB

File metadata and controls

25 lines (15 loc) · 1.55 KB

Migrating from MEA

Apache Asyncband (Incubating) is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Please read the DISCLAIMER.

Asyncband continues the codebase formerly published as mea, but it uses a new Cargo package and Rust crate name. Existing mea releases remain available for builds that have not migrated, but they receive no further development.

Recommended migration path

First, upgrade the existing dependency to mea 0.6.7 and resolve any changes required by earlier MEA releases. The historical changelog documents those releases.

Next, switch from mea 0.6.7 to asyncband 0.6.7 without changing the dependency's feature configuration, and replace Rust paths from mea:: to asyncband:::

# Before
mea = "0.6.7"

# After
asyncband = "0.6.7"

Asyncband 0.6.7 is the compatibility point for the rename, so the dependency name and Rust paths are the only changes expected in this step. No compatibility package or re-export keeps the mea crate name available; downstream crates must update those names directly.

Once the project builds with Asyncband 0.6.7, upgrade through later Asyncband releases separately. Follow the Asyncband changelog and apply the migration notes for each release instead of combining later breaking changes with the rename.

For the background to the rename, see the Asyncband proposal discussion.