Difference between revisions of "Upgrading"

From OpenPLi Wiki
Jump to: navigation, search
(Development strategey)
(How and what on upgrades)
Line 11: Line 11:
  
 
  <u>Major releases</u> (so like 6 => 7) you must flash, preferably using the [[Installation#Flash_from_the_Menu_.28FlashImage_support.29|'''menu''']] and choosing the backup option, then everything is restored after the flash. When there is no Hard disk present use an USB stick.
 
  <u>Major releases</u> (so like 6 => 7) you must flash, preferably using the [[Installation#Flash_from_the_Menu_.28FlashImage_support.29|'''menu''']] and choosing the backup option, then everything is restored after the flash. When there is no Hard disk present use an USB stick.
 
  
 
=='''Release notes'''==
 
=='''Release notes'''==

Revision as of 18:29, 30 June 2020

Development strategey

The current development strategy consists of 3 different versions:

  1. Stable release. This version is deemed suitable for every day use, even if you are a novice or not technically savvy.
  2. Release candidate. These are precursors to a stable release, used for final public testing before creating a stable release. Only use if you want to test and report back issues to the forum.
  3. Development. Images created from the latest development codebase. These are for developers only, unstable, and may break at any point. These versions are not released to the public.

How and what on upgrades

OpenPLi distinguishes between minor releases and major releases. A minor release is when you upgrade from version 7.1 to 7.2 and a major release is when you upgrade from version 6.X to version 7.X. When you want to upgrade, minor and major releases must be approached differently:

Minor releases (so like 6.0 => 6.2) are updates, so updating will suffice! So Main menu > Setup > Software update
Major releases (so like 6 => 7) you must flash, preferably using the menu and choosing the backup option, then everything is restored after the flash. When there is no Hard disk present use an USB stick.

Release notes

When a release comes online, details of what has changed will be in the release notes. At current, the strategy is that before a release there is a pre-release or release candidate (RC). As a pre-release of release candidate is not "the release", there are no details on what has changed as the release notes will only come online with the release.

What can you expect from upgrading

Of course we opt for more stability, look and feel changes, corrections and when vendors have updated drivers, they will be present.

Backup

As always before you upgrade create a Backup, although we test everything thorough. it's always best to do so.