4

It is my understanding that one of the goals of SE is for Q&As to be able to withstand the test of time in terms of their value to future readers. With this in mind (and assuming that the 'new gmail compose' won't always be so new), I'm wondering if there is a way to clarify/make explicit what is meant by 'old version' of X and 'new version' of X other than leaving the reader to look up application updates relative to the date of the original post.

This might be doubly helpful in instances (such as the question below re. Google Maps) in which the "new" application is in an 'invite only' stage.

Examples of where this may be helpful:

One thought would simply be to include screenshots when the questions pertain to changes to the UI.

4

I'm wondering if there is a way to clarify/make explicit what is meant by 'old version' of X and 'new version' of X other than leaving the reader to look up application updates relative to the date of the original post.

Screenshots should be how it must be done, especially considering very few(if at all any) web applications explicity display their version number. Enforcing this, however is near close to impossible, we can probably nudge the OP to include a screenshot.

You must log in to answer this question.

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