Does anyone else "Version Lock" their XY install ?

[GreetingsFromPoland]

hi! after this round of betas and on the next official release i am planning to "version lock" my XY so i no longer will get betas, releases, etc. i am doing this due to the announcement of the upcoming "Glider" feature removal. i use this feature way too often to let it go and am not interested in juggling multiple XY EXEs that contain specific features.

i understand i won't get any further fixes (important) nor new features (less important - especially since they could be removed at a later date). i'm okay with this. my workflow is pretty basic and doesn't change much, so i don't really anticipate missing out on much.

anyway, my question is, does anyone else "version lock" their XY ? if so, what are your reasons ? i see posts from time to time where people are referencing older/previous versions, so i guess it happens, maybe not on purpose. maybe just not checking for updates until they run into a problem ? not sure.

i'm also open to suggestions if there are any. as far as i know, keeping a separate portable copy around would be the only option.

[Horst]

No longer applying updates means not only that you won't get newer functions
but also you don't get errors fixed you may not yet have encountered.
Using a portable version and disable the update checks makes what you want.

[highend]

does anyone else "version lock" their XY ?

No. I'm collection all versions (since v10) in an archive, so whatever I need can be extracted if necessary

i see posts from time to time where people are referencing older/previous versions

Or just because they've bought only a one-year license and don't want to upgrade (and pay again)

keeping a separate portable copy around would be the only option

That's the way you should do it