When you want to stop maintaining something, do you just leave it to slowly fade into obscurity, actively delete it, or something else?
And why did you choose to do it that way?
When you want to stop maintaining something, do you just leave it to slowly fade into obscurity, actively delete it, or something else?
And why did you choose to do it that way?
You could also share the source code, perhaps someone will pick it up and continue developing it
I think it kind of depends on why you are dropping something. I'd probably have the first line of the description state it's no longer supported, and maybe include a link to something comparable.…
If people use it, it seems less than considerate to keep them from using it. You could (should) say that it's no longer supported.
Yet another option is to make the two apps the same.
Really trying to avoid that!
For one of my DataFields, a user so liked the concept and wanted to be able to store different settings for his short runs, long runs, interval sessions, recovery runs etc. that I ended up with a multisport version, four single sport versions and a spare one for CIQ1 users... When I need to do an update it is, believe me, a very tedious task. 
You will doubtless tell me there is a better way to manage discrete settings profiles (and I would love to hear it), but until 3.2 (I think) there was no way to edit DataField settings from the watch. (Not to mention the memory impact of each additional setting.)
