# \[Review, 3rd\] SF-0007: Subprocess

**URL:** <https://forums.swift.org/t/review-3rd-sf-0007-subprocess/78078>\
**Category:** Foundation\
**Created:** [February 25, 2025, 1:07am UTC](https://forums.swift.org/t/review-3rd-sf-0007-subprocess/78078 "2025-02-25T01:07:00Z")\
**Posts on this page:** 1\
**Showing post:** 59

<div class="post-metadata">

**Author:** ![Pippin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/pippin/32/24826_2.png) [@Pippin](https://forums.swift.org/u/Pippin)\
**Post date:** [March 3, 2025, 11:48pm UTC](https://forums.swift.org/t/review-3rd-sf-0007-subprocess/78078/59 "2025-03-03T23:48:36Z")

</div>

As long as it doesn't adopt an unwritten "never make breaking changes" then that seems fine until a major release.

> [@Any plans to merge \`Swift Collections\` and \`Swift Numerics\` into Swift core library?](https://forums.swift.org/t/any-plans-to-merge-swift-collections-and-swift-numerics-into-swift-core-library/77854/28):
>
> It's our goal to never make breaking changes to these projects. In this regard, they are somewhat atypical for open-source packages (at least modern move-fast semver server packages; in the older open-source world this approach was more common). We will not always achieve that, but in general we want them to meet the same source-stability standards as we have for the stdlib.

* * *

Probably for another thread: I vouch that there needs to be some kind of official documentation/Swift Lang Manifesto for non-stdlib (or even Foundation) packages on how evolution of APIs can or should take place. I'm not talking about the forum evolution process, but how package APIs can even be pitched to change in the first place.

If there's no standardization, I don't feel confident that all Swift Lang packages will adhere to similar rules that allow API evolution.

---

_[View the full topic](https://forums.swift.org/t/review-3rd-sf-0007-subprocess/78078)._
