Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from: Version labels for answers As already most of the feedback...
#4: Post edited
by
Alexei
·
2021-12-04T19:47:16Z (over 2 years ago)
add duplication comment
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
- Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
- >= 4.0.1 and <= 7.1
- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
- Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
- >= 4.0.1 and <= 7.1
- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
- **[Edit]**
- This is a duplicate of this ["global" meta post](https://meta.codidact.com/posts/282281). Unfortunately, closing as duplicate indicating a post from another community is not allowed.
#3: Post edited
by
Alexei
·
2021-10-22T19:53:46Z (over 2 years ago)
encoded tag
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
- Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
>= 4.0.1<= 7.1- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
- Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
- >= 4.0.1 and <= 7.1
- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
#2: Post edited
by
Alexei
·
2021-10-16T10:02:28Z (over 2 years ago)
fixed the issue
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
Software Codidact is now small, but as it grows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
- >= 4.0.1
- <= 7.1
- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
- As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from:
- [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers)
- As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement.
- Software Codidact is now small, but as time flows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not.
- Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version).
- **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question:
- >= 4.0.1
- <= 7.1
- An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible).
- Any thoughts on this proposal? Do you think it would help?
#1: Initial revision
by
Alexei
·
2021-10-16T08:25:46Z (over 2 years ago)
Specify framework / library version in the answer
As Stack Exchange (Stack Overflow mostly) is struggling to deal with outdated answers, they came with a proposal that we can learn from: [Version labels for answers](https://meta.stackexchange.com/questions/370640/version-labels-for-answers) As already most of the feedback indicates, the proposed solution seems convoluted and thus hard to implement. Software Codidact is now small, but as it grows, it will suffer from the same disease: answers are getting older and it would be hard for future readers to understand when a specific answer is correct (minimum and perhaps a maximum version for the framework the answer works for) and when it is not. Reactions help to deal with outdated answers, but for major frameworks, some answers can be both correct (still work for those using an older version) and wrong at the same time (not working for those using a newer version). **I am wondering about adding a text field next to the answer that allows the answerer to specify the version the answer applies to.** That would typically mean the minimum version, but the maximum version can also be specified. Examples for an answer to an Angular question: >= 4.0.1 <= 7.1 An even better way would be to clearly separate the minimum version from the maximum one. Both would be optional and free text (to be as simple as possible). Any thoughts on this proposal? Do you think it would help?