Skip to content

Commit 45f388f

Browse files
committed
Revise editorially
Let's clean up whitespace and address and remove the TODOs.
1 parent 3c51473 commit 45f388f

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

content/inside-rust/program-management-update-2025-07.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
+++
2-
path = "inside-rust/9999/12/31/program-management-update-2025-07"
2+
path = "inside-rust/2025/08/05/program-management-update-2025-07"
33
title = "Program management update — July 2025"
44
authors = ["Tomas Sedovic"]
55

@@ -22,14 +22,10 @@ First, I've sent a couple requests for goal updates. This lead me to noticing an
2222

2323
After people provided their final messages, I've published the final 2025H1 Project Goals update:
2424

25-
https://github.com/rust-lang/blog.rust-lang.org/pull/1667
26-
27-
(**TODO** change the link to the published blog if it's merged in time)
25+
https://blog.rust-lang.org/2025/08/05/july-project-goals-update/
2826

2927
With that done, I've closed most of the tracking issues. Some goals are being renewed for the H2 period so we're keeping those open.
3028

31-
(**TODO**: again, make sure we've actually closed the issues before publishing this post.)
32-
3329
## Starting 2025 H2 goals
3430

3531
With all of that out of the way, Niko published the [call for 2025 H2 goal proposals][2025H2CFP].
@@ -46,7 +42,6 @@ Once all the champions are selected, we'll meet with the team leads, go over the
4642

4743
Similarly, we'll take their input regarding flagship goals.
4844

49-
5045
As the goals were being proposed, Niko, Rémy and I looked at the PRs, fixed any CI issues and merged them.
5146

5247
For each team, I've opened a call for champions Zulip thread listing goals that requested their support. [Here's an example for the Lang team](https://rust-lang.zulipchat.com/#narrow/channel/213817-t-lang/topic/2025H2.20Goal.20Review).
@@ -108,7 +103,6 @@ Rust for Linux was a Flagship goal the [second half of 2024][rfl2024h2] as well
108103

109104
[rfl2024h2]: https://github.com/rust-lang/rust-project-goals/blob/main/src/2024h2/rfl_stable.md
110105

111-
112106
[rfl2025h1]: https://rust-lang.github.io/rust-project-goals/2025h1/rfl.html
113107

114108
This effort requires close collaboration with the Lang and Compiler teams, among others, and contact points on both sides to bridge the gap between the two projects. Until now, that was done by Niko Matsakis et al. on the Rust side and Miguel Ojeda et al. on the Rust for Linux side.
@@ -126,7 +120,6 @@ I helped Miguel propose two 2025 H2 goals ([compiler][rfl-compiler] and [languag
126120

127121
This lets Niko disengage from the program completely and focus on the many other things he's doing across the Project.
128122

129-
130123
## Misc
131124

132125
### `ping-goals` retry issue
@@ -147,7 +140,7 @@ As you can see in the thread, this wasn't a new behavior either. Precisely the s
147140

148141
Zulip interpreted this as a timeout and retried the requests a few times.
149142

150-
[Here's the fix he opened][ping-goals-fix].
143+
[Here's the fix he opened][ping-goals-fix].
151144

152145
[ping-goals-fix]: https://github.com/rust-lang/triagebot/pull/2109
153146

0 commit comments

Comments
 (0)