Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete?What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Migration of MSO links to MSE links
Source Link

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? http://meta.stackoverflow.com/questions/156219/what-if-the-answers-of-a-historical-locked-question-become-obsolete#156226What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? http://meta.stackoverflow.com/questions/156219/what-if-the-answers-of-a-historical-locked-question-become-obsolete#156226 indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Suppose an old closed question has an historical lock on it, making impossible to vote/comment/flag on any post.

What should we do if such questions have a high visibility but contains some outdated or wrong information? What if the answers of a historical locked question become obsolete? indicates that such questions should be unlocked (and potentially removed), but what about cases where most of the information is still accurate and useful?

For instance:

What are best practices that you use when writing Objective-C and Cocoa?

I think this post still deserves a historical lock as the information provided is indeed useful. Only little parts of it are gradually becoming outdated and still being hit every time one queries for cocoa best practices.

What should we do when a historical-locked question provides, say 85% of useful up-to-date information and 15% of outdated one?

Post Reopened by Shog9
Slim down, focus on differences from dup
Source Link
Shog9 Mod
  • 454.4k
  • 203
  • 1.3k
  • 1.9k
Loading
added 659 characters in body
Source Link
Loading
edited tags
Link
Shog9 Mod
  • 454.4k
  • 203
  • 1.3k
  • 1.9k
Loading
Post Closed as "Duplicate" by Shog9
Source Link
Loading