JuliaLang / JuliaLang/VersionsJSONUtil.jl
Incorrect S3 ACL
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 5
- Forks
- 8
- Avg merge
- 24d 1h
- Merged PRs (30d)
- 1
Description
From the Discourse post:
Apologies to anybody who ran into issues yesterday; the permissions on the binaries were initially set incorrectly, which cascaded through the multi-step release process in a way that wasn’t visible until the end, leaving things in a weird state. We’ll be working to make the overall process more robust to avoid disruptions in the future.
I figure it's good to have a GitHub issue somewhere, to refer to. I wasn't sure where the correct place to put that issue is, so I put it here for now.
Cross-ref https://github.com/JuliaLang/juliaup/issues/1250. However, that issue is Juliaup-specific, and I think we need an upstream non-Juliaup-specific issue to refer to.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Discourse post and Juliaup issue #1250 to understand the incorrect S3 ACL and how it affected the release process. The issue does not name files, tests, or an entry point, so the work is complete only once a concrete upstream robustness change and its validation are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, julia
- Domain
- release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100