Update Process (Filewalker) + When to update

[baker]

@HeroHann

When do I have to update?
I am running 1.15.3 now and 1.16.1 is out (some people are having problems).
When is my time to absolutely do the switch?

The information you are looking for is in the thread that you linked, first post.

@brandon

• We are going to stop having Tardigrade satellites upload new data to nodes that are two minor releases behind. If you’re running 1.11, but 1.12 is the latest complete rollout (we’re currently rolling out 1.14), then you will continue to get new uploads, but 1.10 and older will not. This is a form of node suspension.
• We are going to start disqualifying nodes that are 3 minor releases behind. In the above example, 1.10 and older will get DQed. We will also be ensuring that the standard source code release will simply refuse to start if it’s 3 minor releases behind.

To summarize, the version numbering works as follows: <major>.<minor>.<bugfix> So when minor is one version behind, you are okay. When it’s two minor versions behind, you are in a form of suspension but you can be redeemed. Three minor versions behind and your node will be DQ’d.

So never be more than one minor version behind and you have nothing to worry about. I don’t know if Storj’s versioning policy allows for skipping minor version numbers (ie. v1.16.1 skips to v1.18.x), but you could probably take the current minor version number from version.storj.io, subtract 1, and that is your allowed version. Your best bet might be to set yourself up a script that polls this value periodically (once per day would be fine) and notifies you when it changes. Or subscribe to the Engineer Discussions category, which is where changelogs are posted. Or subscribe to updates from Github.