itsscb/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo.git synced 2025-10-01 11:30:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

Docs(process/release): Update to include test tools in publication

Browse Source 
Signed-off-by: Paul Mabileau <paulmabileau@hotmail.fr>
This commit is contained in:
Paul Mabileau 2024-02-07 23:39:19 +01:00
parent 6f581e9056
commit 29c45d0e66
No known key found for this signature in database
GPG Key ID: FC16B37F6782B0AA
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/doc/contrib/src/process/release.md
View File

@ -131,9 +131,9 @@ Cargo's library and its related dependencies (like `cargo-util`) are published
to [crates.io] as part of the 6-week stable release process by the [Release to [crates.io] as part of the 6-week stable release process by the [Release
team]. There is a [`publish.py` script] that is used by the Release team's team]. There is a [`publish.py` script] that is used by the Release team's
automation scripts (see <https://github.com/rust-lang/simpleinfra/>) to handle automation scripts (see <https://github.com/rust-lang/simpleinfra/>) to handle
determining which packages to publish. The test and build tool crates aren't determining which packages to publish. The build tool crates aren't published.
published. This runs on the specific git commit associated with the cargo This runs on the specific git commit associated with the cargo submodule in the
submodule in the `stable` branch in `rust-lang/rust` at the time of release. `stable` branch in `rust-lang/rust` at the time of release.
On very rare cases, the Cargo team may decide to manually publish a new On very rare cases, the Cargo team may decide to manually publish a new
release to [crates.io]. For example, this may be necessary if there is a release to [crates.io]. For example, this may be necessary if there is a