1.4. Strawberry 7.0 Upgrade Information

General Upgrade Information

What are the System Requirements?

• Strawberry 7 can only be operated as a Dockerized deployment. Customers who haven’t switched to a Dockerized deployment must undergo these steps first..
• Strawberry 7 must be installed on Ubuntu 24.04.x LTS Server & if necessary, Ubuntu 22.04.x LTS Server.
• The Strawberry Client application does no longer support macOS 11 (Big Sur).
• Strawberry 7 may have new system requirements compared to your current installation. Please check the system requirements!

What Needs to be Updated?

Strawberry 7 is a major version upgrade requiring updates to all software components. This includes…

• the server software (including all proxy encoding nodes)
• macOS & Windows client applications.
• Adobe CC panels.

The latest versions of the client and the Adobe CC panel extension are available on the related section on our website.

What’s the server update process?

The update process can include multiple steps depending on which Strawberry version you are currently running.

If you are already on the Strawberry version 7.0.x

The update is incremental and requires no additional steps.

If you are on Strawberry version 6.6.x

The update is incremental and requires no additional steps. Please note that the upgrade will perform a database upgrade and may take some time.

If you are on Strawberry version 6.4.x (EOL)

1. Updating to 6.4.29 or newer. This can be skipped if you are already on a version newer than 6.4.29.
2. Performing the Strawberry Docker conversion.
3. Updating to 6.6.
4. Updating to 7.0

If you are on Strawberry version 6.2.x (EOL)

1. Updating to 6.4.29 or newer. This can be skipped if you are already on a version newer than 6.4.29.
2. Performing the Strawberry Docker conversion.
3. Updating to 6.6.
4. Updating to 7.0

If you are on Strawberry version 6.0.x. (EOL)

1. Updating to 6.4.29 or newer. This can be skipped if you are already on a version newer than 6.4.29.
2. Performing the Strawberry Docker conversion.
3. Updating to 6.6.
4. Updating to 7.0

If you are on Strawberry version 5.6.x (EOL)

If you are on Strawberry version 5.6.x or older, please contact our support for details regarding the update.

Important and/or Breaking Changes

Strawberry 7.0 is a major upgrade that includes new features and changes to existing ones. Some of these changes might impact your existing workflows, so you should familiarize yourself with them before the update.

API Changes

• API DEPRECATION: The user’s owned team should now be retrieved using the
  owned_team_id attribute instead of own_team_id. The latter will be removed no earlier than the 7.0 release.
• API DEPRECATION: The user’s list of team_ids in the api/v1/teams/user_owned response should now be retrieved as .teams[].team_ids. It is still available at .teams[].users[].team_ids but will be removed no earlier than the 7.0 release.
• API DEPRECATION: The owner (user) of an owned (user) team should now be retrieved using the owner_id on the team, the owned_team_id attribute on User API responses might be removed no earlier than the 7.0 release.
• API DEPRECATION: Successful API responses (status code 200) that currently only return the JSON string ok will be changed to status code 204 with the next major release (7.2).

Preditor EOL/EOS

With the release of Strawberry 7, Preditor has reached the end of support. Strawberry. 7 no longer offers the functionality of importing Predator sequences into Adobe Premiere Pro.