The internet is a lawless place with knowledge and sarcastic wit the pistols of this wild frontier.
Don't go out without being sufficiently armed.


Other places

Ares (Current version: 0.B)

Ares's primary facilities have been moved elsewhere:

  • If you wish to report a bug in Ares, please proceed to its bugtracker.
  • If you'd like to request a feature, register a blueprint.
  • If you have questions or can provide answers regarding Ares's usage, visit the Q&A section.
  • Before you post a new question, you should check the FAQ, though.


  • Mind the forum rules.
  • Due to its documentedly horrible quality, we do not offer NPatch support.

Post Reply 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Feature Requests Suspended
Author Message
Commander-in-Chief Renegade Offline
Lazy Modder

Posts: 1 906
Joined: 21 Nov 2004
Reputation: 14
Post: #1
Feature Requests Suspended
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:
  1. Being requested
  2. Being vetted by us and the community
  3. Being either rejected or accepted
  4. Being either closed for good, or suspended
  5. If it was previously accepted, it will ultimately be scheduled...
  6. ...then implemented...
  7. ...tested...
  8. ...and ultimately, hopefully, resolved & closed

You will notice that the only difference is that the request gets suspended for a while in the middle - other than that, everything stays as it was before. Think of it as being placed on hold.

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

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.
07.08.2010 08:53:46
Visit this user's website Find all posts by this user Quote this message in a reply
Post Reply 

User(s) browsing this thread: 1 Guest(s)