-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meta-RFE: Please add milestones or clarifying labels to all open issues #1147
Comments
Going through all 250 issues will take quite some time:) Although, the idea is great and I completely support it! @vozersky i need you to assist me on this:) |
Honestly, going through the 168! that're currently open is plenty, though, if you want to go through the closed 1s for historical/whatever reasons, be my guest. 😁 |
@TPS the grand issue cleanup&sorting campaign is coming soon :) |
Working on it. What we're doing right now:
Regarding milestones, we do the feature requests and bugs review every time we plan a major release, that's when we assign milestones. |
So we'll have 2.11 and 3.0 for now, everything else will be assigned later |
Maybe not yet close until those "else" assigned? |
I've closed all the obsolete/duplicate/etc issues. All other issues were marked properly (bug/feature request + priority). When we will be planning the next update, we'll consider its priority. |
Recently, thanks to @dennisfong86 bumping it, I was reminded of #533. I realized part of the problem for the issue (which seems simple enough, given #201 has been implemented) is that, though likely accepted (it has UI label, after all), it hadn't been
Milestone
d, & would possibly be forgotten 'til later.I propose @AdguardTeam goes back &
Milestone
all appropriate issues, & keep those updated for these & new issues. This search finds all issues that are not:Milestone
dThe text was updated successfully, but these errors were encountered: