I’m writing this on my return from a week spent with the development team we have in Montreal, Canada. They are currently beavering away on Sibelius, Sibelius | First and Sibelius Cloud Publishing, to bring new functionality and features to all of them. However, these are no longer applications with their own roadmaps, source control streams, and build jobs. These applications—as well as our License Server, Avid Scorch for iOS, and the iOS SDK (which allows anyone to build their very own iPad app to handle native Sibelius files)—are now all on the same roadmap, and share the same code and build jobs.
Our developers have been working hard on unifying the Sibelius applications and solutions. Previously, the apps all had varying degrees of separation from Sibelius, and their own build jobs, meaning we couldn’t update them all without reapplying and replicating the work multiple times.
In recent releases of Sibelius, we’ve been introducing the ability to define new staff sizes, color notes individually, and so on. And those with keen eyes, and an iPad, will have noticed updates to Avid Scorch to support these new features as well. Our applications are now unified, which means that once we add features to the main version of Sibelius and kick off a new build, all of our related apps are built all at the same time with support for the new feature we will have just added, without having to write any more lines of code. This gives us the flexibility to quickly release new versions of all our apps, or just one or two, depending on how suitable the feature is. You’ll soon see new versions of Sibelius | First and Sibelius Cloud Publishing, which will complete this transition.
What does this all mean for you? Well, we used to release upgrades and new features every two years, and we’re now releasing new features every few months. The goal is to continue to release the larger features every few months, but also release smaller fixes when they are ready—saving you from waiting for an important fix you need to help your workflow.
As well as removing a huge amount of technical debt, this allows the whole development team to focus on the features for the right application, and not worry about how the other applications will inherit that change. It frees up the whole team to be more focused on bringing you world class solutions for creating, orchestrating, educating, editing, engraving, and finally, publishing—using just one toolset.
As I wrap up my trip, I’m filled with excitement for the year ahead. We have a solid roadmap for the remainder of the year and a host of ambitious new features coming in 2017 that I can’t wait for you to start using.