This release marks an important milestone: Omniduct is now considered to be stable and feature complete!
This release focussed primarily on improving documentation, and every user-facing class and function is now documented. There were some breaking changes to the `DuctRegistry` API which hitherto has not received much love, but otherwise code changes were fairly minimal.
Features and enhancements:
- Extended the `DuctRegistry` configuration format support, and made minor changes to the API to be more intuitive. [Users of omniduct v0.9.6 and earlier will need to adjust their use of `DuctRegistry` appropriately.
- Added a `show_about` utility function to simplify showing of information about the Omniduct package (or dependent packages), providing the option to "endorse" Omniduct or other significant dependencies.
- Included the new Omniduct logo, which you can feel free to use to endorse Omniduct in your own work.
- Extended documentation coverage to all user-facing classes and methods, and improved the consistency of documentation conventions.
- Added an example company/organisation-specific Omniduct configuration wrapper to assist with the bootstrapping of such wrappers.
Bugfixes:
- Avoid use of `_file_read` in `download` in case the `_open` method was overloaded by clients, as in `LocalFsClient`.