Making games is a team sport – and like any team sport, the team has to train together to play together well, even if the individual players are really good at what they do! We want to get to a 1-week cycle by the end of the year, and I think we know how to do it – we need to make some improvements to our infra and our process and then just lots of practice. A year ago it took us about six weeks to push out a release, and the dates fluctuated a lot. We don't announce these dates to anyone because if they slip, people get annoyed and we have to Explain Things and that's no fun at all.Īlso: it took us a while to get to this point – we had to get the dev teams working together well, we had to get the deployment infrastructure set up, we had to get QA familiar with the project, we had to scale QA to match the dev teams' velocity, and so on. Like, we're targeting next Wednesday to release the version currently in QA, but if something turns up before now and then (and it sometimes does! That's why we have QA, so they turn things up!) it might slip until Thursday or Friday, and if everything goes absolutely smoothly we might be able to release it already on Tuesday. The project I work on is on a pretty regular 3-week cycle at this time, but even we can't predict exactly when a build is out of QA. My interpretation for their silence is that the patch is currently in QA, and they don't want to give an exact date for when it'll be out of QA, because if you do that, there's a big risk that either it'll slip, or you'll have to release it in a worse state than you'd like. I'm also eagerly waiting for the first patch! But no, if I'm honest I expected more information regarding the first patch the game desperately needs Its a good read and I found it interesting.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |