Participants
- Konrad
- Franz
- Adam
- Dianna
- Gwynne
- Joannis
- Josh
- Seb
- Sven
- Tim
Notes
Carry over
-
@tachyonics to refactor the Swift.org post -
@tachyonics Create GH issue for SwiftPM feature to allow multiple conflicting major versions and start forums post about it
-
@sebsto To check if AmazonLinux2023 is working on 6.1 now. Last time check there was a build issue, needs some prerequisites to get build running, not had enough time recently.
- Likely action on this only in second part of July
-
Adam talked to Fabian about reviewing AWS Lambda PRs
- Sebastian requesting someone review PRs so we can do a stable release; Fabian not available to do that so we need to find some others
- Konrad, Franz and others in SSWG offered to do the reviews when pinged
- Adam can have a look since he had some experience with it
- This is holding off the 2.0 release.
- Adam will not be available this week, until mid-June, but from there spend one hour together on the runtime reviews
- Questions are about using NIO async stream or not, and such questions.
- Parked until AWS less busy in next weeks.
-
Goals post
- Franz, Sebastian: We have a writeup but checking in with developer experience workgroup
- Our draft prepared: https://forums.swift.org/t/swift-server-workgroup-2025-annual-update/78504
- Seb to confirm with contributor experience work group and we'll post on the forum
-
SE 0461 Run nonisolated async functions on the caller's actor by default
- Are there any concerns about this?
- Konrad: No, we're quite happy about the not hopping off in server apps because it'll make less hopping
- For example this will be nice so we don't have to do more
- This is different than the "main actor by default", which doesn't affect us in server use cases either way.
Misc topics:
- Tim: Server Side Swift conference
- submit proposals!
- Sven: Package index - will start android and wasm compatibility testing soon
SendableMetatype- Franz: you may hit this, this is about isolated confrmance
- Likely increase in 6.2 warnings, we'll see after new Xcode is released.
- We'll check Swift 6 warnings once we have them
- Tim to check how many new warnings in Vapor in 6.2
- Konrad: specifically interested in the sendable metatype causing issues or not, we should communicate this is a thing and suggest how to approach it to library authors.