Renegade
07.08.2010, 08:53:46
In our ongoing quest to bring down the flood of feature requests to a manageable level, we have decided to take the logical next step and suspend all accepted new feature requests for the moment.
With DFD tackling the accumulated existing feature requests, and Accelerated Feature Fate introducing quicker vetting of new requests, this ensures that even those requests which are newly selected for implementation by us and the community don't clutter the tracker and compete with already scheduled issues for attention.
Ideally, with this last measure in place, after the DFD, we will achieve a situation on the tracker where all open issues are either being worked on, or scheduled to be worked on, with no "zombie-issues" cluttering it.
Let me emphasize that this measure is temporary. Given the volume of requests, it will likely be in place for a while, but ultimately, we hope the workload will allow us to schedule accepted new requests immediately again.
So for the time being, a feature request will run through the following stages:
By tomorrow, we'll have a warning up on the submission page to inform users of this decision.
As usual, we'd be happy if we didn't have to do this, but until we get more coders to share the workload with, there's simply no point in adding more and more and more issues to the queue while we have a hundred issues still scheduled for implementation.
On the bright side, however, with all these recent request management events and process changes, we should have tamed the vast amount of feature requests very soon, and will launch into a period of strong focus on a long chain of requests the community truly wants, with frequent, small releases produced with little distraction from garbage issues.
And I believe we can all look forward to that.
In related news, Rounds 1 and 2 of the DFD are almost all judged, and the Ultimate Smackdown will commence next week at the latest.
With DFD tackling the accumulated existing feature requests, and Accelerated Feature Fate introducing quicker vetting of new requests, this ensures that even those requests which are newly selected for implementation by us and the community don't clutter the tracker and compete with already scheduled issues for attention.
Ideally, with this last measure in place, after the DFD, we will achieve a situation on the tracker where all open issues are either being worked on, or scheduled to be worked on, with no "zombie-issues" cluttering it.
Let me emphasize that this measure is temporary. Given the volume of requests, it will likely be in place for a while, but ultimately, we hope the workload will allow us to schedule accepted new requests immediately again.
So for the time being, a feature request will run through the following stages:
- Being requested
- Being vetted by us and the community
- Being either rejected or accepted
- Being either closed for good, or suspended
- If it was previously accepted, it will ultimately be scheduled...
- ...then implemented...
- ...tested...
- ...and ultimately, hopefully, resolved & closed
By tomorrow, we'll have a warning up on the submission page to inform users of this decision.
As usual, we'd be happy if we didn't have to do this, but until we get more coders to share the workload with, there's simply no point in adding more and more and more issues to the queue while we have a hundred issues still scheduled for implementation.
On the bright side, however, with all these recent request management events and process changes, we should have tamed the vast amount of feature requests very soon, and will launch into a period of strong focus on a long chain of requests the community truly wants, with frequent, small releases produced with little distraction from garbage issues.
And I believe we can all look forward to that.
In related news, Rounds 1 and 2 of the DFD are almost all judged, and the Ultimate Smackdown will commence next week at the latest.
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.