Any time you are updating an existing deployment to a new version of the OS or the client software, the best practice is to first deploy this in a limited environment to not only test your approach to the updates, but then to be able to confirm that all your critical workflows and functionality are working as you expect.
With the number of configurations that are possible with our products, it is extremely important that you are validating your use case before deploying any updates across your fleet/installation. It’s possible that certain upgrades could impact the behavior of your players and finding that out when the update is only deployed in a lab environment (recommended) or on a small number of players will allow you to make an informed decision on whether to proceed with the update(s) or not.
To update the OS on your players, see New Device Setup, Device Activation, and Device Provisioning.
Finding and Using Release Notes
Current BrightSign OS and BrightAuthor:connected release notes are available on our website. We provide release notes to help you determine what exactly is in the release and to help identify possible areas of your evaluation. For example, if there was a new feature in the area of the software you rely on, you may want to spend a bit more time evaluating that area of your particular use case to ensure that your workflow and functionality hasn’t changed.
Each release notes document is divided into New Features, Improvements, and Bug Fixes:
- New Features are completely new pieces of functionality that have been added.
- Please note that some new OS features may only be available through custom scripts and not BrightAuthor:connected, but may become available through BrightAuthor:connected at a later time.
New features in BrightAuthor:connected may rely on a specific or newer OS. This isn’t always the case, but it is something to be aware of.
- Improvements are changes made to improve accessibility or ease of use for existing features.
- Bug Fixes are resolutions to issues in the OS or client software. We only announce fixes for problems that are found in public releases of OS or software.
Beta Releases
BrightSign will also occasionally make Beta releases available. These releases have NOT been tested by our QA team but contain functionality that users might want to access instead of waiting for an official release. Beta releases can be public, which means that they are available to anyone who wants to download and test them, or private, which means that they are only given to customers who might need certain functionality. Beta versions have important new features and bug fixes, but they may also contain known or unknown stability issues. If the reliability of your digital signage system is more valuable than new features and improvements, wait until those features become available in an official version.
BrightSign rarely releases an automatic update to the operating system. However, if your player is running a version of the operating system that is lower than required for operation with BSN.cloud, and the BrightSign player is not running an autorun, an automatic update will be pushed to your device during the provisioning process.
Warning
The data storage system in use by Chromium processes changes when there is a major upgrade to the Chromium version bundled with the BrightSign OS. While updating to a newer version of the OS is generally stable, there are cases where downgrading the OS can cause the data accessed by Chromium to be inaccessible. Other data not in use by Chromium that can be stored on SD, SSD, USB connected and external devices that contain media, systems files and other data do not share this limitation. Please be sure to test your workflow for any OS upgrades or downgrades before deploying to a production environment.
Open Source Licenses and Other Notes
- BrightSign player operating systems use many open-source licenses. The applicable open-source licenses and code are available here.
- Older versions of BrightAuthor:connected are generally compatible with newer OS versions. This means that you can update the OS on your players even if you don’t want to republish the presentation using a new version of BrightAuthor:connected, but we still recommend deploying to your lab or test device(s) first to confirm this before pushing any updates broadly to your fleet.
- Previous OS releases are available on this page.