Skip to content

2025h1 project goals April update #1614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
May 26, 2025
Merged

Conversation

lqd
Copy link
Member

@lqd lqd commented May 21, 2025

This is the April 2025h1 project goals update. It's not late at all!

I summarized the All Hands update, turned the async update into its TL;DR, and massaged the RFL one to fix a couple issues.

r? @nikomatsakis

Rendered

Copy link
Contributor

@nikomatsakis nikomatsakis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better late than never, I always say!

Copy link
Contributor

@apiraino apiraino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't read but found two tiny typos :-p

Copy link
Contributor

@apiraino apiraino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@lqd
Copy link
Member Author

lqd commented May 26, 2025

@senekor what's the procedure now to land posts? I only saw the 9999/12/31 date being described in the blog post generator, but then what do we do, once approved we change the date? But what are the "aliases" and who/when are they filled?

@senekor
Copy link
Contributor

senekor commented May 26, 2025

Yes, once the date of publication is known, just change it in the path variable of the front matter, that's it.

Why are you asking about the aliases? (So I can improve documentation about it, depending on what's causing the confusion.)

The aliases are used to preserve permalinks from before the Zola migration. The custom generator used <date>/<slug>.html for the permalink, but Zola doesn't support that intentionally. Only via the aliases feature can we redirect old links to the new ones (<date>/<slug>/, without .html).

Also, the release announcement posts have an additional alias so you don't have to search for a specific post, you can just enter /releases/X.XX.X in the URL bar for the version you want.

Other than that, aliases should not be used. I've seen some new posts created that copy-pasted from old posts to bootstrap the front matter, which then also added the "backwards compatibility" alias to the new post. That's not necessary, but it also doesn't really hurt.

@lqd
Copy link
Member Author

lqd commented May 26, 2025

Yes, once the date of publication is known, just change it in the path variable of the front matter, that's it.

Good, thanks!. So I can now do that.

Why are you asking about the aliases?

Because I also initially wanted to start this post by copying the previous month's post, and it has aliases. I tried to find documentation about the process and couldn't find much apart from the generator code.

@lqd
Copy link
Member Author

lqd commented May 26, 2025

Alright, the publication date is set to today. Hopefully someone can merge soon.

CI seems to be failing for unrelated reasons (GH is having issues).

@senekor senekor merged commit d93f500 into rust-lang:master May 26, 2025
8 of 9 checks passed
@lqd lqd deleted the april-goals-updates branch May 26, 2025 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants