In that case, is there any plans for your processes to change to get a more rapid release-cycle? Going dark for N months to implement a feature seems to fly in the face of the workflow GitHub tends to inspire.
Sometimes you're on a rapid release cycle making non-user facing changes that will allow you to release new user-facing features. I have no idea if this is what was going on at Github, but I've been at plenty of places where the code and/or infrastructure was so messed up, seemingly trivial updates would take weeks and months to complete.
