In the RFE tracker, whats the difference between "Needs_decision, Needs_planning" and especially between "Next minor" and "Next release"? Do we not always add new features to A+1 or B+1, but not to C in Version A.b.c?
And: How to handle priorities in RFE tracker? I know how we deal with them in bugs tracker. And: Do we not have "accepted" as status in RFEs? AFAIK we have it with bugs.
Some insight and common guidelines appreciated.
J.M.
J. M. a écrit :
In the RFE tracker, whats the difference between "Needs_decision, Needs_planning" and especially between "Next minor" and "Next release"? Do we not always add new features to A+1 or B+1, but not to C in Version A.b.c?
Hi J.M.
I think that the confusion comes from "minor". For me, current major is 4, current minor is 0, so next minor is 4.1.
But we could just have "next release".
And: How to handle priorities in RFE tracker? I know how we deal with them in bugs tracker. And: Do we not have "accepted" as status in RFEs? AFAIK we have it with bugs.
Priorities are a vague indicator of the importance of the feature request.
If it's marked "next release", it means it has been accepted, right?
I don't know whether we need "rewrite".
Some insight and common guidelines appreciated.
Hi
Dne Mon, 1 Jul 2013 09:59:59 +0200 "J. M." mynetx@users.sf.net napsal(a):
In the RFE tracker, whats the difference between "Needs_decision, Needs_planning" and especially between "Next minor" and "Next release"? Do we not always add new features to A+1 or B+1, but not to C in Version A.b.c?
I don't really think these have sensible values as they were mostly set by reporters or by us quite long time ago.
And: How to handle priorities in RFE tracker? I know how we deal with them in bugs tracker.
I think we don't handle it anyhow.
And: Do we not have "accepted" as status in RFEs? AFAIK we have it with bugs.
The states are same in both tracker and I don't see accepted status either of the trackers.
-
J. M. -
Marc Delisle -
Michal Čihař