Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

Release Notes for DuraCloud releases beyond 4.1.0 are now captured in GitHub:

https://github.com/duracloud/duracloud/releases

Legacy Releases

...

Release 4.1.0

Released: July 18, 2016

The DuraCloud 4.1.0 release makes it possible to support storage in both the DPN and the Chronopolis systems independently. Support for storing content in DPN through Chronopolis remains, but this release opens the door for storing content in Chronopolis alone, for scenarios where storage in DPN is not appropriate.

...

  • User experience improvements when snapshots are taken, providing more immediate information and snapshot detail.

  • Improved performance for downloading manifests of large spaces.  Please note:  manifests are no longer sorted by default.  

  • Improved Sync Tool performance through checkpoint frequency reduction.

  • Reduced Sync Tool download size and startup time.
  • Users with USER role can now view streams on open spaces.
  • Improved error handling in queue deposit processing
  • Improved bridge notifications
  • To see the full list of changes, or for more details on specific changes in release 3.7.0, see the JIRA issue tracker.


 

Tip
titleBrowser Support Note

DuraCloud currently supports all of the major web browsers: Chrome, Safari, Firefox, and Microsoft Edge. As of version 3.7.0, DuraCloud no longer supports Microsoft Internet Explorer. This change is in response to Microsoft's recent end of support announcement for Internet Explorer. This shift allows development effort to be focused on delivering the highest quality user experience for the vast majority of our users. If you are still using Internet Explorer, we recommend you consider moving to one of the supported browsers mentioned above.

 


Release 3.6.0

Released: November 23, 2015

...

  • The Duplicate on Ingest service is now the Duplicate on Change service.
    • This service now supports all of the same on-ingest features as before, but it now also performs duplication of all update and delete actions as well. This allows the primary and secondary cloud stores to be kept completely in sync.
  • The Bulk Bit Integrity Service has been improved.
    • This service has been updated and verified to properly handle spaces with up to 1 million items
    • The second step of the MD5 verification, which used to run locally on the instance, has been moved to hadoop, allowing the service to complete much more quickly for large data sets.
  • User management functions have been removed, as they are now performed by the DuraCloud Management Console.
    • As a convenience, administrators are still able to see the list of users and their roles within the DuraCloud Administrator UI.
  • Service outputs have been made more consistent.
    • All DuraCloud services which produce an output file now store that file in the x-service-out space.
    • Services which produce log files store those logs in the x-service-work space.
    • The names of the output files have been made more consistent, making it simpler to determine which files correspond to which service deployment.
  • Password security has been improved.
    • All passwords used within DuraCloud are now immediately pushed through a hashing function before being are stored, so that no user passwords are transferred or stored as clear text.
  • A ServiceClient is now available, to compliment the StoreClient and make it easier to make direct API calls to manipulate DuraCloud services.

...