Remember the 15th of November, when the Avalon team completed over 50 points in a single sprint? This sprint finally got us moving towards new features for Avalon 3.0. A big priority is master file management; we were able to make some big strides in making sure the system can move, leave in place, or delete master files. Our next sprint will focus on making Avalon aware of where files and derivatives are being stored.
Our November 14 webinar was superb! With zero technical glitches and great questions and feedback, we felt it was a success. Jon Dunn (Project Director, IU), Mark Notess (Product Owner, IU), and Julie Rudder (Product Owner, NU) led the webinar.
If you were unable to attend, don't fret. The webinar recording and slides can be viewed at your leisure.
This week was all about refinement. We started work on refining a new skin for the MediaElement.js player so that the player has nice sizable buttons that are optimized for both desktop and touch browsers. We refined and finished testing our migration tools and documentation for the various installation methods, so if you installed Avalon 1.0 you should be only six steps away from using Avalon 2.0! We also started on one of our big priority stories for Avalon 3.0, which is to skip the transcoding step for media that has already been processed.
With Avalon 2.0 ready for public consumption, the team spent this sprint working on documenting our migration paths for the different installation methods. Our last two sprints have been devoted to setting up the distribution of our releases so we talked quite a bit about how to streamline the process so we can hit our releases more efficiently. The team looked into our new media player, MediaElement.js, some more to figure out how to contribute new features and bug fixes. We have a plan!
We post insights from the Avalon team and guest writers about the Avalon Media System. Start reading to learn more about our team, development process, and more!
Contact Us | Facebook | Twitter | Listserv | RSS