Release of OMERO.server 5.6.2, OMERO.web 5.7.0 and OMERO.iviewer 0.10.0

Today we are releasing OMERO.server 5.6.2 which fixes installation instructions for CentOS 7,
adds installation instructions for both OMERO.web and OMERO.server on CentOS 8 and Ubuntu 20.04,
and finally drops support for Ubuntu 16.04 and removes the corresponding installation instructions.
We are also releasing OMERO.web 5.7.0 and OMERO.py 5.7.1 which both contain some API additions.

OMERO.server 5.6.2 runs in the same deployment environments as OMERO.server 5.6.0 and
the Bio-Formats Memoizer cache will be invalidated.

Installing the Software:

For full details of the changes with the OMERO 5.6 series see the
OMERO 5.6.0 release
announcement. Full documentation for this release is available
under https://docs.openmicroscopy.org/omero/5.6.2/.

OMERO.server 5.6.2 is available from
archived downloads.
OMERO.web 5.7.0 and OMERO.iviewer 0.10.0 are both available from PyPI.
These have been tested with
OMERO.py 5.7.1 so we
recommend that you upgrade OMERO.py on both server and web deployments.

Official Docker images are available as usual on Docker Hub with either
the latest or the 5.6 tag:

OMERO.server

  1. The OMERO 5.6.2 release includes a bugfix to import-as by group owners (see #94)
  2. Upgrades the version of Bio-Formats from 6.3.1 to 6.5.1 includings substantial improvements and fixes to various imaging file formats, see Bio-Formats version history for more details

OMERO.web

  1. Adds JSON API support for Experimenters and Groups (see the JSON API documentation)
  2. Adds ROI and Shape support to paths_to_object, see #159 and #178
  3. Fixes several bugs to the webclient

A new version of our OMERO.insight is also available.

See the OMERO.web 5.7.0 changelog for more details

You are invited to discuss this announcement on
the image.sc forum.

All the best with your upgrades,

The OME Team

4 Likes

This is great. Does the Docker image of omero-web-standalone run OMERO.web 5.7.0 despite the 5.6.2 tag? Will try to test this out over the coming days.

@mdug

Thanks for pointing that out. The wrong version number was used. I have now pushed a new Docker image with the correct version number

Cheers

Jmarie

1 Like