Hi everyone,
All throughout the Swift codebase there references to Radar bugs (just do a search for “rdar" on the repo). As far as I am aware, these are all still private/internal. Is this the case? If so, is there any plan to migrate bugs on Radar to bugs.swift.org <Issues · apple/swift · GitHub?
FKL
Hi everyone,
All throughout the Swift codebase there references to Radar bugs (just do a search for “rdar" on the repo). As far as I am aware, these are all still private/internal. Is this the case?
Yes.
If so, is there any plan to migrate bugs on Radar to bugs.swift.org <Issues · apple/swift · GitHub?
Not in general. They sometimes contain proprietary information from submitters, who never agreed that they be published on swift.org, so we can’t just do a blanket push. That said, we’ve already moved a number of the issues to Jira (and will probably keep pushing out others) which are general bugs and feature enhancements that can be made less sensitive.
Also, while radar numbers are frequently included in testcases, they are only their to allow book-keeping and do not replace the need to explain why a change is made. To be more concrete, we don’t consider it to be acceptable for an Apple person to commit a bug saying “this fixes rdar://1234” without explaining what the patch is, what it does, etc. Also, we generally dislike radar numbers in the source code for the compiler themselves, they should be in testcases only. I don’t think we’re 100% clean on this though.
As the swift community grows, it is reasonable to expect other organizations with proprietary (or just “different”) bug trackers to contribute to swift. As they do, it is perfectly reasonable to add their tracking numbers to testcases as well.
-Chris
On Dec 9, 2015, at 5:21 PM, Frederick Kellison-Linn via swift-dev <swift-dev@swift.org> wrote: