Skip to content
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

Add information about versions and dependencies #57

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add information about versions and dependencies #57

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
34bf378
Add information about versions and dependencies
0xTim Jul 21, 2021
5886d2f
Fix PR comments
0xTim Dec 6, 2023
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
3 changes: 2 additions & 1 deletion process/incubation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,7 @@ Changes to the Swift Server Ecosystem index page will be announced by the SSWG u
* Ecosystem
* Uses SwiftPM
* Integrated with critical SSWG ecosystem building blocks, e.g., Logging and Metrics APIs, SwiftNIO for IO
* Note that you are **not** required to only depend on packages in the incubation process but you should only include dependencies where they are necessary. Package authors are responsible for ensuring the security of dependencies and must be able to fix any issues if dependency authors are unresponsive to security issues.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels like separate or sub-dot for the how to handle dependencies?

Maybe dependencies is a separate section/discussion entirely? And here we'd just say that a package is allowed to depend on non-sswg recommended libraries?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

* Longevity
* Must be from a team that has more than one public repository (or similar indication of experience)
* SSWG should have access / authorization to graduated repositories in case of emergency
Expand All @@ -158,7 +159,7 @@ Changes to the Swift Server Ecosystem index page will be announced by the SSWG u
## Graduation Requirements

* [Minimal Requirements](#minimal-requirements)
* Have stable API (no pending/planned breaking API changes), with at least one published major release (e.g. 1.0.0)
* Have stable API (no pending/planned breaking API changes before submission), with at least one published major release (e.g. 1.0.0). Breaking changes are allowed following semantic versioning rules, but major versions should not be released regularly to aid adoption.
0xTim marked this conversation as resolved.
Show resolved Hide resolved
* Support new GA versions of Swift within 30d
* CI setup for two latest Swift.org recommended versions of Swift
* CI setup for at least one of Swift.org recommended Linux distributions
Expand Down