<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On Dec 21, 2015, at 11:17 AM, Chris Lattner via swift-dev <<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 8:31 AM, William Dillon via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Now that I’ve published a tarball of the ARM swift compiler, I’m getting some messages about this or that not working. I’m curious about the intended usage/audience of <a href="http://bugs.apple.com/" class="">bugs.apple.com</a>. Should I encourage people to file bug reports, or do you only want bugs relating to the supported platforms in there?</div></div></blockquote><br class=""></div><div>I think it’s fine to file bugs around larger community projects, so long as they’re on a track to becoming part of the <a href="http://swift.org" class="">swift.org</a> effort (i.e. you don’t intend it to be a permanent fork).</div><div><br class=""></div><div>-Chris</div></div></blockquote><div><br></div><div>I agree.</div><div><br></div><div>To further add to what Chris said, note that contributions to support a port don't need to remain in a fork before the platform becomes "officially supported". We'd prefer that the necessary work to support a port happens in the main repository if possible. People can use forks to do experimentation, etc., but once the bring up starts reaching some critical mass I think it is valuable to get those changes into the main repository long before the port is "done".</div><div><br></div><div>Ted</div><div><br></div><br><blockquote type="cite"><div><br class="">
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=cUTXn2XUQg0NGOEWHTVTyDr9W6Is2djHPo9bUJUJ-2FRYWTbkyZ641V2HE-2FRsAimj0Q5-2FJNHbq1tfsLlvOzuc8oNxFr5U6n5hPyfTQp9sh89hbzd6qSGVRa0stnO-2FncQ4Uwl-2B9Osmgyzma0qXQXVqXQ0iyrB4rP7NX1Ih-2FL8WjP1Q3dBPpuFP-2FSsyeVJREE1Zn-2BlOhVozF9eeij-2BkyqWMffXx6pmuztmUycIddxrMgL-2Fo-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-dev mailing list</span><br><span><a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></span><br></div></blockquote></body></html>