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

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question. An example of a question using this m.o. is "Can I change my profile picture using the API version 2?Can I change my profile picture using the API version 2?" on Stack Apps.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question. An example of a question using this m.o. is "Can I change my profile picture using the API version 2?" on Stack Apps.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question. An example of a question using this m.o. is "Can I change my profile picture using the API version 2?" on Stack Apps.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

Example of such a question
Source Link

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question. An example of a question using this m.o. is "Can I change my profile picture using the API version 2?" on Stack Apps.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question. An example of a question using this m.o. is "Can I change my profile picture using the API version 2?" on Stack Apps.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.

Source Link

If a question is specifically about change in a technology, it isn't a duplicate.

If an answer to a given question has been made obsolete by a new version of a technology or regulation, you can ask and self-answer a new question that's specifically about the new version.

In the question: Avoid closure as duplicate by including the version number of the relevant change in the new question's title, citing the old question, and ideally citing the particular change that made the old question's answers not apply. It might look similar to the following:

The solution described in question "How do I do whatever?" works for Product 5.3, but someMethod() was deprecated in Product 5.6.

The link in this notice will put the new question into the "Linked" section of the old question.

In the answer: Stack Exchange uses the same Creative Commons license as Wikipedia. So feel free to adapt someone else's answer to the old question into your self-answer to the new question, so long as you cite that answer and its author.