<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hey, Brian. Re: your <a href="https://bugs.swift.org/browse/SR-1613?focusedCommentId=14864&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14864" class="">comment about labels</a>:<div class=""><br class=""></div><div class=""><blockquote type="cite" class="">By the way, I'm curious for your thoughts on the swift-3.0 label, which I introduced in <a href="https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160516/000662.html" class="">https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20160516/000662.html</a>. I've seen you "curate" labels in the past, so I hope I didn't step on your toes by creating one. I tagged this task as "swift-3.0" because it's a sub-task of <a href="https://bugs.swift.org/browse/SR-710" class="">SR-710</a>, which is also marked "swift-3.0" – we want to be able to generate tests lists before shipping corelibs-xctest.</blockquote></div><div class=""><br class=""></div><div class="">I knocked the "swift-3.0” label off because this was the first time I’d seen it in a non-corelibs issue, and because I wasn’t sure we had committed to doing this <i class="">particular</i> subtask in Swift 3—or rather, I wasn’t sure the <i class="">SourceKit</i> team had committed to doing this in Swift 3. I feel weird having release labels assigned by people working in other parts of the project because it feels like forcing the SourceKit engineers to fix it. I know that (a) wasn’t your intention, and (b) is probably accurate—as in, if this alternate solution hadn’t come up <i class="">someone</i> would have had to do something—but I reacted to it anyway and removed the label.</div><div class=""><br class=""></div><div class="">I do think now it was a bit of a knee-jerk reaction, so I apologize. As you noted, I’ve generally been the one adding labels, and removing or standardizing some of the ad hoc ones input by issue reporters; in this particular case that led to an instinct to remove a label I hadn’t seen rather than thinking about it. Certainly active contributors should be able to introduce new labels they find useful.</div><div class=""><br class=""></div><div class="">SR-1613 is resolved, so it’s kind of a moot point now, but do feel free to add useful labels in the future. If it matches one I’ve seen before I might standardize it, but I won’t remove them. Or if I do I’ll at least comment about it. :-)</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><div class="">P.S. “swift-3.0” also doesn’t match my naming convention for labels, which is UpperCamelCase, but given that I didn’t write it down anywhere or tell anybody I can hardly complain!</div></body></html>