Just ran across this post, which was bumped by Community for having been unanswered. However, it was answered by Jeff (no upvotes), along with a tag. I gave an upvote so that it wouldn't be bumped again. But, Community should ignore those posts, since they have an official answer.

Possible exceptions, as pointed out by random, are the statuses planned and deferred.

Statuses bydesign, completed and declined should be ignored by Community.

share|improve this question
    
Evening? It's more like late afternoon. (But yes, timezones and majority of audience and all that) –  random Aug 1 '09 at 6:59
add comment

4 Answers

up vote 17 down vote accepted

Community♦ really should know to leave well enough alone some times.

status-planned or status-deferred might be interesting to float up to the front now and then until they get switched over to status-completed or status-declined.

share|improve this answer
1  
And maybe not bump closed questions so we can close and not see things like this get bumped: meta.stackoverflow.com/questions/37262/… as it did just now. I can see stirring old questions/requests/etc. so they don't get lost in the shuffle. –  AnonJr Feb 27 '10 at 23:33
add comment

completed stuff should have at least one answer with an upvote, so we know our "completion" wasn't total B.S. that everyone hates.

share|improve this answer
add comment

I actually think we should go even further here on Meta and completely disable automatic bumping by the Community user. Bumping was supposed to get some additional attention to questions in the hopes of getting additional answers, but I don't think that it makes sense on a discussion site.

share|improve this answer
    
Not for the community, but the devs probably should see when a bug report is updated (i.e. with better repro steps). –  Dana the Sane Aug 1 '09 at 20:29
1  
Well when a real person edits the post to improve it, that should definitely bump it. I was talking about the automatic bumping back to the top of the front page by the Community user. –  Kyle Cronin Aug 1 '09 at 20:36
    
Since we don't allow duplicate discussion questions, I think it's important to have those old discussions bumped every now and then. –  Lance Roberts Feb 27 '10 at 16:55
1  
I was thinking about this and I like it, but I would add an exception for feature requests. I think posts tagged feature-request with no status-* tag should get bumped from time to time, to encourage voting on them. –  Joel Coehoorn Mar 7 '10 at 4:31
    
I think that bumping some questions doesn't make sense, for example the ones tagged faq. If one of those questions don't have an up-voted answer, they would be bumped all the time from the Community user, and voting an answer for those questions doesn't normally make sense (if it's not for sorting the answers). –  kiamlaluno Aug 28 '11 at 10:43
add comment

Considering the pace at which questions land off the first page on meta (really slow), having something that's irrelevant only adds noise. They really should not be bumped back up if they've been completed, I completely agree.

share|improve this answer
    
(somebody spotted this as a dup, so I merged your answer into this older question) –  Marc Gravell Jan 16 '10 at 10:35
    
@Marc Gravell Thanks for that! –  alex Jan 16 '10 at 12:47
    
I wish I could give you another +1 for being my first @name notification ;-p –  Marc Gravell Jan 16 '10 at 19:24
add comment

You must log in to answer this question.

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