<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><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="">Looks good indeed!<div class=""><br class=""></div><div class="">I have few questions:</div><div class="">- what is purpose of `paging:*` labels, to help people see issues they are interested in? How it’s different from assignees (which can be multiple)?</div><div class="">- why “bug” has “ezyang planning to delete this tag”. I’d prefer to have “type: bug” and other “type:*” labels as: “type: discuss”, “type: enhancement”, “type: question”, and maybe more as e.g. stack has <a href="https://github.com/commercialhaskell/stack/labels" class="">https://github.com/commercialhaskell/stack/labels</a> </div><div class="">- how priority labels interact with milestones?</div><div class="">- Should we add “pr welcome” or “awaiting pr” for issues which are discussed, but nobody have interest or time implementing right away (will help new contributors especially when combined with `meta: easy`)</div><div class=""><br class=""></div><div class="">- Oleg</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 11 Jul 2016, at 08:09, Mikhail Glushenkov <<a href="mailto:mikhail.glushenkov@gmail.com" class="">mikhail.glushenkov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi,<br class=""><br class="">On 11 July 2016 at 06:37, Edward Z. Yang <<a href="mailto:ezyang@mit.edu" class="">ezyang@mit.edu</a>> wrote:<br class=""><blockquote type="cite" class="">If you hate it I can change it back but give it a try for now.<br class="">If the "component" prefix in "component: solver" is too long we could go for<br class="">something like "C-solver" but I think that is less transparent.<br class=""></blockquote><br class="">Thanks, looks much better than the previous version.<br class=""><br class="">Re: the "specification" tag, I think it's supposed to mark proposed<br class="">changes to the .cabal file format and GHC/Cabal interaction (i.e. the<br class="">Cabal spec).<br class="">_______________________________________________<br class="">cabal-devel mailing list<br class=""><a href="mailto:cabal-devel@haskell.org" class="">cabal-devel@haskell.org</a><br class=""><a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel" class="">http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel</a><br class=""></div></blockquote></div><br class=""></div></body></html>