Skip to content
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

Closed
TPS opened this issue Apr 2, 2017 · 7 comments
Closed

Meta-RFE: Please add milestones or clarifying labels to all open issues #1147

TPS opened this issue Apr 2, 2017 · 7 comments

Comments

@TPS
Copy link
Contributor

TPS commented Apr 2, 2017

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 Milestoned, & 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:

  • Closed
  • Milestoned
  • Labeled:
    • Question
    • Waiting for Data
    • Bug
@ameshkov
Copy link
Member

ameshkov commented Apr 2, 2017

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:)

@TPS
Copy link
Contributor Author

TPS commented Apr 2, 2017

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. 😁

@vozersky
Copy link
Member

vozersky commented Aug 18, 2017

@TPS the grand issue cleanup&sorting campaign is coming soon :)

@ameshkov
Copy link
Member

ameshkov commented Nov 16, 2017

Working on it.

What we're doing right now:

  1. Handling all the new unlabeled issues
  2. Cleaning up old unanswered questions (in process)
  3. Setting up stricter rules on bug reports/questions.

Regarding milestones, we do the feature requests and bugs review every time we plan a major release, that's when we assign milestones.

@ameshkov
Copy link
Member

ameshkov commented Dec 4, 2017

So we'll have 2.11 and 3.0 for now, everything else will be assigned later

@ameshkov ameshkov closed this as completed Dec 4, 2017
@TPS
Copy link
Contributor Author

TPS commented Dec 4, 2017

Maybe not yet close until those "else" assigned?

@ameshkov
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants