Symphony.

You knew something big was coming.

When you read that birds were falling from the skies by the hundreds and that Symphony’s birthplace had been inundated by biblical floods, you could be forgiven for thinking that the end of days might be upon us.

2010 has been a great year for Symphony. It wasn’t until fellow working group member, Nick Dunn had put together a list of achievements did it dawn on me just how much we have managed to achieve in a year. Without further ado, let’s take a look at some of those accomplishments.

For the first taste of what promises to be an ongoing supply of Symphony documentation hot sauce, two new articles are ready for your enjoyment.

Just a brief note to announce the release of Symphony 2.1.2, which includes some important security improvements, performance enhancements, and bug fixes.

We are honoured that the judges of the McFarlane prize recognised our ongoing efforts and have given us the encouragement to continue improving the website.

It’ll take longer than seven days, but boys and girls, there’s going to be a Symphony book.

Stephen Bau, head of Symphony’s Advocacy Working Group, has a question for the community: Can Symphony get some love?

Symphony 2.1.1 maintenance update is upon us. This time around, we knew we had to be more vigilant with getting updates out in a timely fashion. While we didn’t expect to see as many issues as our previous major update releases, the development team had put aside two weeks to monitor any issues after a 2.1 launch.