Sergio Gasquez Arcos

> Implementing a test CI-Workflow that builds a daily all target image, for consumption in all downstream CI projects. We should test here if it makes a difference uploading this...

I see a few options: - `Xtensa_1.73.0.1-RISCV_nightly-2023-11-01` - `all-2023-11-01` - Xtensa and nightly version can be inferred from the date the container was built - `esp-rust-nigthly` or similar - Skip...

Note for future me, if we end up changing anything, we should update https://esp-rs.github.io/book/installation/using-containers.html

> i am fine with option 3 though this would imply that we build the all container always only with latest xtensa-rust and not with any other version, i think...

Wow! Thanks for the updates, that's a great improvement!!

The [following conversation on Matrix](https://matrix.to/#/!LdaNPfUfvefOLewEIM:matrix.org/$TfuIb3K2TSwKVWMz3aXlkT5-hKvwHqLgqHieRh5YWJ4?via=matrix.org&via=tchncs.de&via=mozilla.org) has good information that can help when writing this section

Hi, we are more than happy to accept contributions! Definitely, this is something that we will need to solve.

For reference, we could use: - https://gitee.com/espressif_systems as mirror of esp-idf and other github dependencies - And we could upload release binaries to AWS like we do in: https://github.com/espressif/idf-installer/blob/main/.github/workflows/update-index.yml

We could publish the toolchain release artifacts to AWS.

Just a small update on this, on [yesterday's community meeting](https://github.com/esp-rs/rust/discussions/163#discussioncomment-5177365) we discussed this issue. We will be probably creating a mirror of our Xtensa Rust and LLVM artifacts, probably in...