How swiftlang/swift-evolution works
Main Components
a) Proposal Management System
• Proposals Directory (containing all .md proposal files)
• Proposal Templates
• Release Documentation
• Vision Documents
b) Process Flow Components
• Proposal Submission
• Review Process
• Implementation Tracking
• Release Management
Key Relationships to Highlight
• Proposal Flow:
• Template → New Proposal → Review → Implementation → Release
• Version Management:
• Proposals → Release Notes → Version Documentation
• Vision Documents:
• Long-term Goals → Specific Proposals
• Swift Evolution System |
• Templates | | Proposals | | Releases | | Visions |
• > | | --> | | <-- | |
• Swift | | - Active | | - Changelog | | - Embedded |
• SwiftPM | | - Implemented | | - Version Docs | | - Macros |
• Rejected | +------------------+ | - Testing |
• ^
• Process Controls |
• Contributing |
• Review Process |
Metadata Layer
• Version tracking
• Proposal numbering system
• Cross-reference links between related proposals
• Implementation status tracking
• The systematic nature of Swift's evolution process
• Clear workflow paths from proposal to implementation
• Relationship between proposals and releases
• Long-term vision integration with concrete proposals