You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 151
Next »
Current and Previous Releases
Release 6
January 2017 - Replacing Fedora 3 with Fedora 4; feature parity with Release 5
- Fedora 3- Fedora 4 Migration tool with reporting
- Preparation for SAAS Pilot
- Develop AWS infrastructure map
- Additional transcode engine support
- Support for Amazon Elastic Transcoder
- Improvements to Playlists
- Faster loading between playlist items
- Track Scrubber: more granular scrubbing for playlist items and structural metadata segments
- Documentation & Transparency
- Improved manual installation and upgrade instructions
- Move JIRA to Waffle/Github
- Fedora 4 Upgrade Path instructions
- Documented migration path from Variations
- Code style guide and standards
- Set RuboCop profile as part of build
- Improve packaging
- Create ansible solution and docker containers (internal only)
- Better developer install methods
Release 6.x
Spring 2017. Bug fixes and improvements to 6.0
- Easily Edit/Import Structural Metadata
- Continued work on AWS integration/support
- Simplification of Development environment (e.g. nginx, ffmpeg transcoding)
Release 7
Move to Hyrax/ Modern Hydra Stack
- Spotlight integration and implementation
- Integrated Automated Test environments
- Investigate HLS on all platforms and its implications
- Create one player view in Avalon
- Re-implement media element customization against the main branch
- Adjust streaming security model
- Move to standard mediaelement
- Better internal permissions setup
- Gemification/Break interdependencies
- Streaming gem for another repo app
- Bulk metadata/editing gem
- Structural Metadata Improvements
- move a master file to a different item
- Better local transcode support
Release 8
TBD - feature list in flux
- Publishing Out to External Media Sites
- Dynamic Adaptive Streaming
- Deeper integration with Hyrax Community
- Further gemification/shredding of core components
Technical work to schedule:
- Packaging/deployment, e.g. use of Docker. Improving installation experience.
- Scalability issues that may arise
- Automated functional testing
Unscheduled Features
- Collections based group management
- Collections based master file handling
- Administrative metadata (owner, digitizer)
- PBCore/DublinCore crosswalks
- Import media from other sources
- Image content/auxiliary items (how does Avalon fit with other initiatives?)
- Integration with oral history tools