What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

Possible Duplicate:
Why don't all bugs and feature-requests have moderator status tags?

I recently asked this feature-request question on meta SO and am wondering when it will be addressed and marked as either or . Is there a defined time-frame for , or does it just depend on availability?

I did try to search for this, but didnt find anything relevant.

share|improve this question

marked as duplicate by random May 20 '12 at 2:07

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

    
In 6-8 weeks, we're told. –  Rosinante May 19 '12 at 20:31
    
Probably tomorrow, or in a few years. Maybe never. Who knows? –  lunboks May 19 '12 at 20:35
    
@Rosinante, ok, thanks, but its not documented anywhere? I couldnt find it. –  Brady May 19 '12 at 20:35
2  
Seems like there should be another status then, maybe something like status-in-progress. Is that worth another feature-request that may never get addressed :) –  Brady May 19 '12 at 20:38
    
the only think for sure is that dumb proposals will be declined right away within few minutes/hours of posted, for the rest see the ans of Pekka –  ajax333221 May 19 '12 at 20:40
1  
@Brady There's [status-planned], though it doesn't get a lot of use. –  Anna Lear May 19 '12 at 20:42
    
If you're really lucky, it only takes 4 hours. –  Dennis May 19 '12 at 21:55
    
6 - 8 weeks, if you're lucky :) –  The Anti-Santa May 19 '12 at 22:56

2 Answers 2

There are currently 10,135 questions tagged with .

Of those, 7,882 of them have not been marked completed, declined, or otherwise.

Just to give you some perspective, there are lots of feature requests. They tend to gravitate towards the ones that are very popular (or very unpopular) and actually make sense to them when it comes to investing their time.

Another thing to keep in mind (don't know if this actually relates to you): don't mark accepted answers on your meta posts if it hasn't actually been resolved yet. The answer may be good and represent a valid way of achieving something, but if you still expect the feature to actually get implemented, you shouldn't mark the question itself as "answered." That makes it look like you've accepted an alternative and the feature you requested is not necessary.

share|improve this answer
    
Thanks for that, I imagine they get alot of feature-requests. I was wondering about having accepted a feature-request answer and how it would affect the status of it. What you mention makes sense. I think there are several points here worth documenting in the FAQ, how should I go about proposing them? –  Brady May 19 '12 at 20:50

Not the answer you're looking for? Browse other questions tagged .