COPY/PASTED FROM HERE:
https://brightsign.atlassian.net/wiki/spaces/PID/pages/797311259/CMS+Partner+Best+Practices
From Based on our experience, partners that follow these practices have the most successful BrightSign integrations:
We want you to have a stable OS build that works for you. We encourage partners to When possible, partners should try to use the latest BrightSign OS builds in order to take advantage of the latest bug fixes and newest features. Running the latest OS build also enables partners to more easily expand their deployments with our latest hardware.
We are continuously improving the firmware on our players, but as is often the case with software, sometimes problems are inadvertently introduced. A stable player is paramount to any BrightSign integration, so we strongly encourage partners to thoroughly test any BrightSign firmware releases
before upgrading players being used in production.
We want you to report any issues so we can help you resolve them. Contact Contact integrations@brightsign.biz for support. ← SHOULDN’T THIS BE support@brightsign.biz?
Partners, not their customers, should communicate with our support team if there is an integration issue.
Partners should try to use the latest OS builds if possible to get the latest bug fixes and newest features. This also allows partners to easily upgrade to our latest hardware.
We To ensure ongoing alignment between BrightSign’s technologies and partners' goals, we encourage partners to talk to us before making major changes to their existing integration, to make sure that BrightSign and the partners are aligned.
Partners should be aware that BrightSign may not fully test experimental features in components such as Chromium. This may affect stability if If those experimental features are used as part of the integration, stability may be adversely affected.