Re: [w3c/manifest] Preparing for Candidate Recommendation (#865)

> Process-wise, we probably should label everything that _isn't_ "defer" to "CR" and then drop the use of "defer". Otherwise, any new issue that gets filed will be considered for CR (and we'd like to have that list shrink over time, rather than grow with any new issues that people file).

@mgiuca We decided to move all CR-labeled issues into the new CR milestone (https://github.com/w3c/manifest/milestone/1) and keep the Defer label. All issues are now either part of the milestone or marked with Defer. New issues should then either be assigned to the milestone or the Defer label, issues that belong to neither of which are untriaged.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/865#issuecomment-633552972