Software versions

[NilsRune]

Why are for example the software version 7.1.3 (29.6.2016) ready for download and update before 7.0.9 (1.8.2016)? When I look at the Software-option under Device when I am about to update my PA-3020, I get confused when I see for example version 7.1.2 one day and 7.0.7 the next day.

My only guess why it is like this, must be the version installed, for example 7.0.x, is the version that you continues to update from. Like if you have 7.0.6 installed, then you update to 7.0.7, but if you have 7.1.1 installed, then you update to 7.1.2.

Then my question would be...why not update from 7.0.6 and to 7.1.2?!

[reaper]

Hi

Once a major version is branched off of a preceding code train, it becomes standalone and both will follow their own release schedule from there on out. Some code trains may see quicker or slower maintenance releases as their age progresses or when urgent updates need to be made available. A specific major release also doesn't seize to exist once a new version is available, and new updates and fixes will keep getting added for the duration of that version's life cycle (usually 3-4 years)

[NilsRune]

But should I update to the newest, in this case 7.1.3, regardless of the version I am running today?

[reaper]

there are several schools of thought regarding upgrading to a newer major release 🙂

for example:

pro: a newer major code train will have new features, that may be useful or even necessary within your environment

con: a newer major release may also be 'young' in that it has not been available for very long, which holds a slightly higher risk of bugs not having been discovered and fixed yet

So while upgrading to the latest and greatest may be a good idea in plenty of cases (new features, improved functionality,...), you may opt to stay with a lower major release with a longer track record until the latest and greatest has reached a certain maturity. (if you are bound by SLAs I'd recommend waiting for x.x.4 or .5 before moving to a new major version)