Rust version policy: add proposed 2025H1 flagship goal

Signed-off-by: Miguel Ojeda <[email protected]>

Author: ojeda

src/Rust-version-policy.md

@@ -10,7 +10,7 @@ To ameliorate that, the kernel is now being [build-tested](https://rustc-dev-gui
 
 Thus, with the pre-merge CIs in place, those projects hope to avoid unintentional changes to Rust and `bindgen` that break the kernel. This means that, in general, apart from intentional changes on their side (that we will need to workaround conditionally on our side), the upcoming Rust and `bindgen` versions should generally work. This applies to beta and nightly versions of Rust as well.
 
-In addition, one of the three [flagship goals for 2024H2](https://rust-lang.github.io/rust-project-goals/2024h2/index.html#flagship-goals) of the Rust project is getting the kernel into stable Rust (at least solving the main blockers).
+In addition, one of the three [flagship goals for 2024H2](https://rust-lang.github.io/rust-project-goals/2024h2/index.html#flagship-goals) of the Rust project was getting the kernel into stable Rust (at least solving the main blockers). A continuation of that work is being proposed as a new [flagship goal for 2025H1](https://rust-lang.github.io/rust-project-goals/2025h1/goals.html#flagship-goals).
 
 [^rust-is-stable]: To clarify, the Rust language is stable, i.e. it promises backwards compatibility, except for those unstable features.