Should swift compiler bugs now be posted as github issues or Radars?

I have a reduced case for an automatic initialiser inheritence compiler bug, but I'm flummoxed as to where I should be posting it, as a Github issue or as a Radar/bug report?

Answered by KMT in 93069022
From swift.org h t t p s : / / swift.org/community ~ contributing


Reporting Bugs

Reporting bugs is a great way for anyone to help improve Swift. The open source Swift project uses Jira for tracking bugs. Our Jira instance is located at h t t p : / / bugs.swift.org/

Accepted Answer
From swift.org h t t p s : / / swift.org/community ~ contributing


Reporting Bugs

Reporting bugs is a great way for anyone to help improve Swift. The open source Swift project uses Jira for tracking bugs. Our Jira instance is located at h t t p : / / bugs.swift.org/

Does this mean we should no longer be using the Apple Bug Reporter for any Swift-related issue, but instead go through bugs.swift.org?

Since the build within Apple's SDK is NOT necessarily going to be the same build that is

currently open source, you should continue to use Apple's bug reporting mechanisms

here. If your issue is with the release at swift.org, the bug reporter there would be

appropriate.

Should swift compiler bugs now be posted as github issues or Radars?
 
 
Q