How should we handle highly rated but out-dated answers to still-relevant questions?
Example:How to delete a module in Android Studio(It's a good 1 year old question with 17,878 views)
Android Studio just left alpha and has been changing weekly for the last year. The above question is still very valid, but the best answer has changed as the tool has evolved.
The best answer for:v0.1 has 57 upvotes (and is the 'accepted' answer)v0.5 has 10 upvotesv0.8 has 1 upvote (from me 10 minutes ago)
In this case, nobody in their right mind would be using an older unstable alpha version, so the accepted & popular answers are just plain old... but the new-correct answer may never surpass the original answer in votes by the time it itself is obsolete. The best answer to this question is the most current one, but it has the least reputation and that probably won't change.
Feature-request - Allow answers to be retroactively tagged with a version.
I know version tagging using the current tag mechanism is frowned-upon (What are the guidelines for using version-specific tags?) for good reasons, but usability is suffering without a good solution and answer-debt will surely increase over time.
