What kind of changes are supposed to be accepted? There is a bunch of regression issues (mostly since 5.4) (e.g.,SR-14988, SR-14815) recorded in the issue tracker, but also many others.
(Not wanting to derail this thread, butโฆ I always wonder if anyone is working on the behemoth of Linux-related issues? And how do we know if someone works on something? I have a bit of fear that bugs.swift.org is turning into the nirvana the Apple Rdar tracker is.)
Whilst the merge window is open, everybody can open a pull request against the swift-4.2-branch in swift-corelibs-foundation or swift-corelibs-xctest on Github. To keep the process smooth and lightweight, the release managers will only consider pull requests that
are bug fixes,
have already been merged to master ,
pass all the unit tests on swift-4.2-branch , and
contain at least one unit test exercising the changed code.
We expect most bug fixes to be small corrections, so creating the pull request might be a matter of creating a branch followed by git cherry-pick -x FIX-COMMIT-FROM-MASTER-SHA . We do realize not all backports will be a conflict-free cherry picks but we hope the community works together to deliver the most pressing bug fixes in a timely manner.
(Replace master --> main and swift-4.2-branch --> release/5.5)