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

Consolidate "Mid term" and "Long term" milestone into a new "Backlog / Help needed" milestone #10632

Closed
mattab opened this issue Oct 2, 2016 · 4 comments
Labels
RFC Indicates the issue is a request for comments where the author is looking for feedback.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Oct 2, 2016

I don't really understand anymore why we have two milestones for stuff we won't work on any time soon: Mid term and Long term. Therefore I'd like to suggest to consolidate these two into one new milestone that is more clear that we could maybe call something like Backlog / Help needed.

It would be useful because:

  • Mid term / Long term distinction is very arbitrary and not real
  • We won't work on the Mid term issues in the mid term (whatever it means?). At best we will work on 10-20% of them over the next two years.
  • the industry term for issues that are not being worked on now is Backlog
  • we will need serious external / business help in order to make progress on these issues, so it would make sense to me to call out and add Help needed in the milestone title.

If nobody disagrees I'll go ahead and make the change in few days...

  • I'll add a label to the issues currently in Long term (for example Long term...) so that we can still have the distinction that these issues are less important than those without the label, in case we'd like to handle them differently in the future.

As always, any feedback is very welcome! 👍

@mattab mattab added the RFC Indicates the issue is a request for comments where the author is looking for feedback. label Oct 2, 2016
@mattab mattab added this to the 3.0.0-rc milestone Oct 2, 2016
@mattab
Copy link
Member Author

mattab commented Oct 2, 2016

@hpvd
Copy link

hpvd commented Oct 3, 2016

good idea :-) With this maybe one can apply a 3-step priority label

  • High priority (should be done as fast as possible ("Killer"/"Blocker", but no concrete milestone applied yet)
  • mid priority (pretty important but no "Killer"/Blocker")
  • low priority ("nice to have" should be done sometime)

Would give even more overview/control what should be thought of next...

@hpvd
Copy link

hpvd commented Oct 3, 2016

Some of the "High priority" ones has of course already "major"-label...
Working with" x-priority" wording one easily could identity every label belonging to this group ("priority") of labels.
.

@mattab
Copy link
Member Author

mattab commented Dec 5, 2016

Done, new milestone: https://github.com/piwik/piwik/milestone/20 listing 1,099 issues
and a new label for lower priority issues: https://github.com/piwik/piwik/labels/Lower%20priority (used to be "Long term" issues)

@mattab mattab closed this as completed Dec 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RFC Indicates the issue is a request for comments where the author is looking for feedback.
Projects
None yet
Development

No branches or pull requests

2 participants