Like 2011 and 2012, we resolved more bugs than we created
in 2013. That's three years in a row! I've never seen that happen
on a project I work on.

There are a lot of people braving Bugzilla to write up bugs.
Skimming the list, I see developers, non-developers, Support
contributors, localizers, support team and a lot of people I
don't recognize.

Here's some number comparisons:

name

2011

2012

2013

Bugs created:

1357

938

889

Bugs resolved:

1637

1025

1116

Total commits:

1137

916

1138

Code contributors:

19

23

32

I spent a good chunk of 2013 working on Input, but here's what I remember
from SUMO development in 2013:

We rearranged the codebase for better Django 1.4 layout. That was a
project. Oy.

We added support for non-English languages to the support forums!

We switched email to be HTML formatted. We also reworked email to be
localized.

We switched to Google Analytics.

We implemented Open Badges---though there's still a few important
pieces to finish there.

We switched to YouTube for videos.

We added support for Webmaker and Firefox OS. Thunderbird support
will be added to SUMO in 2014.

Mike took a lantern, a crust of bread and a big sword and spelunked
into the darkest dungeons filled with stinky, squelchy muck and
rewrote the showfor code.

We reworked our search code to handle multiple indexes, though we
haven't taken advantage of that, yet.

We switched deployment to use Dennis to
lint all translated strings before pushing them to
production. This has almost assuredly saved us from production
fires. I hated those kinds of fires. Hooray for Dennis!

We overhauled everything to add support for Persona
authentication, but had to push off deployment indefinitely
because of problems with Persona which are being ironed out by the
Persona team.

We added an escalation system for questions that haven't received
a response in x hours for some positive value of x that is still
in flux.

We ditched Highcharts.

We wrote a command-line deployer which tells us exactly what's going
out and tells New Relic, too. This gives us a much better idea of what
we're deploying and how it affected the site afterwards. This command-line
deployer is named chief-james
in honor of James who has moved on to greener and well measured pastures.