Skip to content

Add support for processing evolution proposals for additional projects #49

@stmontgomery

Description

@stmontgomery

We recently launched a Testing Workgroup in Swift, and as part of that, we're beginning to place proposals focused on Swift Testing in a new /proposals/testing subdirectory of the swift-evolution repo.

As of swiftlang/swift-evolution#2721, that subdirectory now exists and contains historical proposals which were approved before Swift Testing began formally participating in the evolution process.

Shortly after that landed, someone realized swift-evolution-metadata-extractor had broken and was no longer successfully processing proposal updates. @hborla landed a quick fix for that issue in #48, which simply ignored all content in the /proposals/testing directory.

This issue tracks adding formal support for including the proposals in that directory and showing them on the Swift Evolution Dashboard. That includes:

  • Finding proposals in the /proposals/testing subdirectory, or perhaps in any subdirectory of /proposals (to future-proof, if desired).
  • Adjusting anything else which may be necessary to successfully parse the header of these proposals. Hopefully there isn't anything materially different, but if there is, that should be accommodated. (Swift Testing uses a distinct template from Swift and SwiftPM, although its header is quite similar.)
  • Ensuring that Swift Testing's custom "ST-NNNN" prefix is handled correctly. (It's intentionally different than "SE-NNNN".)

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions