Skip to content

Fixing Typos in 2019-11-12 Infrastructure Team Meeting #465

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.

Sign up for GitHub

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 1 commit into from
Nov 25, 2019
Merged

Fixing Typos in 2019-11-12 Infrastructure Team Meeting #465

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions posts/inside-rust/2019-11-18-infra-team-meeting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,17 +11,17 @@ Attending: alexcrichton, kennytm, Mark-Simulacrum, pietroalbini, sgrif, shepmast

## Rust 1.14.0 Cargo artifacts on the rust-lang-ci S3 bucket

Following on last meeting’s topics, pietroalbini investigate whether it would
Following on last meeting’s topics, pietroalbini investigated whether it would
be possible to redirect requests for Cargo 1.14.0 from the `rust-lang-ci` S3
bucket to our CDN. The answer is no, as the S3 support for redirects requires a
different endpoint than the one included in the manifest. The two main courses
of action were to nothing (keeping the files in the `rust-lang-ci` S3 bucket),
of action were to do nothing (keeping the files in the `rust-lang-ci` S3 bucket),
or to rewrite and resign the manifest of Rust 1.14.0 to point to the CDN.

Mark-Simulacrum was in favor of doing nothing, but pietroalbini pointed out
keeping releases in two different places will make mirroring and caching
efforts more complex, as mirror authors will have to special-case a separate
domain just for a release. We then decided to rewrite and resing the manifest.
domain just for a release. We then decided to rewrite and resign the manifest.

shepmaster proposed to add a test somewhere to ensure this doesn’t happen
again, but nobody on the team had the time to do this. If someone is interested
Expand Down