- @MarshallOfSound
- @codebytere
- @nornagon
- @jkleinsc
- @ckerr
- @sofianguy
- M73 into
5-0-xor6-0-x#16876
- Verdict: Merge M73 into
5-0-x- We should not consider this to have set a precedent for future decisions
- Question: Does this change our timeline for 5.0.0 stable?
- No, we don't believe it will
- Question: external comms?
- Update the issue, close the issue after M73 has been merged into
5-0-x*No need for blog post
- Update the issue, close the issue after M73 has been merged into
- Question: should we enable
sccacheon macOS release builds?
- Verdict: We will enable
macOSrelease builds - Mitigating attack vectors
- Separate bucket with separate S3 keys
- Authenticated get?
- Periodically burn & regen keys?
- Enable versioning on the bucket
- Script to verify we don't have more than 1 version
- Separate bucket with separate S3 keys
- Question: should we include docs changes in release notes?
- Verdict: Yes, but not in their current form.
- Specific details have yet to be determined.
- Right now we just include the PR numbers. is this useful?
- Other options
- List of contributors names at the end of the release notes?
- Linkify people's github handles and put them next to the notes?
- It's important that we value non-
feat/fixchanges
- Proposal: new style of release notes generation
- Proposal For Change 🔗
- Technical challenge is updating PR comments, which is a part that doesn't already exist.
- Something like this would be good.
- Let's keep working on the proposal & make a prototype.
- Discuss how we're going to avoid the M73 scenario in future.