Attendance
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.
Deployment guides
- @0xTim and @tiborbodecs to join website WG to sync up
swift-aws-lambda-runtime
@Adam-fowler will talk to Fabian
Moving swift-aws-lambda-runtime from swift-server
- @FranzBusch move things closer to "home"
- @jbelkins can move it to AWS labs
- someone from AWS has to admin it (e.g. Seb or Josh)
- @FranzBusch could also s.o. else have write access (merge, approve)
- @jbelkins to check if policy allows it
Agenda
-
@FranzBusch need to provide guidance around package traits
- Doc team & Joe Heck thinking about guides
- observability is an example where traits are useful
- add dependency and use traits to opt out
- this could be a SSWG guidance document
- @Ben_Cohen these are stringly typed things, we should think about proposing guidance around naming
- @FranzBusch does a trait introduce API breaking changes?
- @Ben_Cohen probably not
- but it could be tricky
- discussion around embedded as an example
- @FranzBusch need to put out guidance around this (more than naming)
-
@FranzBusch min version support / semver
- @0xTim typically current -2 (5.10, 6.0, 6.1)
- discussion around semver rules / API breaking changes
- recommend API check in CI
- @finestructure what's the rationale behind current -2?
- @FranzBusch time based, partly also b/c Xcode versions are difficult to support further back
- discussion around CI
-
@FranzBusch goals for 2025
- we're not doing blog posts anymore
- we should post this to the forums in the next week or so