# Rust 1.74.0 pre-release testing

**URL:** <https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865>\
**Category:** announcements\
**Created:** [November 13, 2023, 1:49pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865 "2023-11-13T13:49:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\
**Post date:** [November 13, 2023, 1:49pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/1 "2023-11-13T13:49:23Z")

</div>

The 1.74.0 pre-release is ready for testing. The release is scheduled for November 16. [Release notes can be found here.](https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1740-2023-11-16)

You can try it out locally by running:

```plaintext
RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable

```

The index is [https://dev-static.rust-lang.org/dist/2023-11-13/index.html](https://dev-static.rust-lang.org/dist/2023-11-13/index.html).

The release team is also thinking about changes to our pre-release process: we'd love your feedback [on this GitHub issue](https://github.com/rust-lang/release-team/issues/16).

---

<div class="post-metadata">

**Author:** ![PoignardAzur](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/poignardazur/32/6464_2.png) [@PoignardAzur](https://internals.rust-lang.org/u/PoignardAzur)\
**Post date:** [November 13, 2023, 2:11pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/2 "2023-11-13T14:11:38Z")

</div>

Are we ever going to address the "This blob took too long to generate" problem, or it going to be stuck in procrastination hell for the next three years?

My suggestion:

- We create a new file named `RELEASES_EDITION_2021.md`, and copy-paste everything from 2021 onwards into that changelog.
- Once 2024 arrives, we create a new file named `RELEASES_EDITION_2024.md`, and so on.
- We add a link to these changelogs at the top of `RELEASES.md`.

That way we have a natural way to split files, and we don't break links to previous releases either.

---

<div class="post-metadata">

**Author:** ![Philippe](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/philippe/32/10779_2.png) [@Philippe](https://internals.rust-lang.org/u/Philippe)\
**Post date:** [November 13, 2023, 3:15pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/3 "2023-11-13T15:15:31Z")

</div>

Why not provide this link instead : [1.74.0 | Rust Changelogs](https://releases.rs/docs/1.74.0/)

---

<div class="post-metadata">

**Author:** ![CAD97](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cad97/32/3460_2.png) [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Post date:** [November 13, 2023, 7:57pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/4 "2023-11-13T19:57:59Z")

</div>

> [@Philippe](#):
>
> Why not provide this link instead

In short, because releases.rs isn't an official publication of the Rust project. It could be adopted given agreement between the team and the current operator, but that's not the case yet.

> [@PoignardAzur](#):
>
> we don't break links to previous releases either.

That's not completely true. "Deep" links to `RELEASES.md#version-release-date` would no longer link directly to the relevant heading. Though if the file completely stops ever rendering, the links are effectively broken anyway.

Unless you're suggesting to forever duplicate the contents between RELEASES and RELEASES\_EDITION, which causes its own issues due to having to manually update and keep those separate files in sync.

---

<div class="post-metadata">

**Author:** ![notriddle](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/notriddle/32/14082_2.png) [@notriddle](https://internals.rust-lang.org/u/notriddle)\
**Post date:** [November 13, 2023, 10:17pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/5 "2023-11-13T22:17:21Z")

</div>

A relatively simple approach to work around the problem would use the existing docs infrastructure:

> <https://github.com/rust-lang/rust/pull/117888>
>
> Preview: http://notriddle.com/rustdoc-html-demo-5/release-notes/releases.html
> 
> …
> This is a workaround for #101714 on top of being a useful addition in its own right. It is intended to change the "canonical URL" for viewing the release notes from GitHub, which is relatively slow, to a pre-rendered HTML file that loads from the same CDN as the standard library docs. It also means you get a copy of the release notes when installing the rust-docs with rustup.

---

<div class="post-metadata">

**Author:** ![simonbuchan](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/simonbuchan/32/9390_2.png) [@simonbuchan](https://internals.rust-lang.org/u/simonbuchan)\
**Post date:** [November 14, 2023, 1:40am UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/6 "2023-11-14T01:40:06Z")

</div>

I assume the OsStr(ing) encoded bytes stabilized APIs are a simple rename of the existing "os\_str\_bytes" apis?

---

<div class="post-metadata">

**Author:** ![PoignardAzur](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/poignardazur/32/6464_2.png) [@PoignardAzur](https://internals.rust-lang.org/u/PoignardAzur)\
**Post date:** [December 5, 2023, 1:37pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/7 "2023-12-05T13:37:40Z")

</div>

I've created a PR with the approach I mentioned:

> <https://github.com/rust-lang/rust/pull/118280>
>
> Split RELEASES.md into new RELEASES\_2021\_EDITION.md file
> 
> To ensure that split…ting the file didn't break formatting, I ran the
> following commands:
> 
> \`\`\`sh
> pulldown-cmark \<RELEASES\_2021\_EDITION.md \>rendered\_2021.html
> pulldown-cmark \<RELEASES.md \>rendered.html
> diff rendered.html rendered\_2021.html | rg "^\>"
> \`\`\`
> 
> At first the diff included multiple new lines in \`rendered\_2021.html\`,
> indicating links that weren't rendered to HTML because their target was
> missing. After I added those targets, but diff was remove-only.
> 
> The general policy for RELEASES files would be to update the \_2021
> file until edition 2024 comes, then we'd create a RELEASES\_2021\_EDITION
> file (also linked from the RELEASES.md file), and so on.
> 
> We could optionally add a RELEASES\_2018\_EDITION and/or a RELEASES\_OLD
> file. Whether we should do that is outside the scope of this PR
> (and I'd appreciate if we could avoid bikeshedding it here).

> That's not completely true. "Deep" links to `RELEASES.md#version-release-date` would no longer link directly to the relevant heading. Though if the file completely stops ever rendering, the links are effectively broken anyway.

That might be more clear by looking at the PR, but my point is that the RELEASES.md file becomes a "legacy" file that stops being updated. So existing links are fine, and new updates go into RELEASES\_XXXX\_EDITION.md files.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\
**Post date:** [March 4, 2024, 1:38pm UTC](https://internals.rust-lang.org/t/rust-1-74-0-pre-release-testing/19865/8 "2024-03-04T13:38:21Z")

</div>

Closed on March 4, 2024, 1:38pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
