Looks like I get to go first with the new regular devblogs. Wish I had some real news. Content and Programmers get all the sexy new stuff to talk about, so I’ll address one of the issues I’ve seen on the forums recently: the lack of bug fixes reaching the network recently.
This actually has little to do with Minecraft, despite popular belief. Yes, for a few weeks Alive was being used for the Colossus alpha testing, but we have had bigger problems involving the hardware. We had a succession of network configuration problems that started back in february when we moved to the network’s new hardware. This, if you remember, coincided with a move to a new hosting location, and Alive moved too. After we had fixed that in early March, Alive was merged with Surface and became the Alpha test server for Colossus. This lasted until the end of march/beginning of april when it came back to us again. However at this time, various hardware components failed, and not all at once either, that resulted in Alive being down for the rest of april while we obtained and configured replacements. We finally got Alive back to normal about 2 weeks ago.
All in all, this has been as aggravating for us in Polaris as it has for you. You should see what this has done to our list of known defects (a public list of these is in the works, and coming Soon™).
So what does Alive being down have to do with bug fixes and patching? Well, before we release any patch to the network we test it thoroughly on an in-house (yes we do test it, honest!! ). With no in-house, i.e. Alive, we had no way of testing any patches for release to the network.
Talking of thorough testing, Polaris is still expanding. Interestingly, our pre-patch ‘awesome’ checklist has expanded as well, and it still takes the entire team about 6 hr’s to test everything, not including the tests we have to spread over two days because of timers.
So, there you have it. After 2 and a half months of test server issues we can now, hopefully, implement our plans for regular bugfix patches.