I'm curious about a part of process for having patches released and would appreciate it if someone from SD or GPG would be kind enough to comment. I'd like to use an older example to ask my question. Let's say SD decides that they want version 1.1 to go live. They have a meeting for what should be in 1.1. They come up with exact items that should be included, balancing requests, exact fixes, etc. I think of it as a list with everything that has to be completed for 1.1. Once the list is compiled, GPG assigns a developer or team to create builds with the new content. I believe they send builds to SD and SD puts those changes through QA. I believe they are constantly getting builds as features are completed, but I'm not exactly sure how all that works. Eventually, GPG has everything on their list checked off and a final build is completed. This is sent to SD for QA. If it doesn't pass QA, GPG will fix and send a new build. If it does pass QA, a release is scheduled and rolled out.
Am I wrong about anything so far? Ok. So, let's say version 1.1 passes QA and is released and a show stopper bug is found. No need to get specific, but something is found after SD considered the version complete. Is GPG responsible for fixing the bugs that were created as a result of the version they coded or does SD have to shell out some more money because it was missed in QA?
I ask all of this because I'm curious about the process. But I'm also wondering if we might be able to assist in beta testing patches again as they are availble.
NT
Well phrased, thoughtful question as usual Pacov. You are a much needed voice of reason around here. +1
lets just wait and see if this will be commented on.
They will if they like. They've been quite open in the past, but surely don't monitor the forums everytime I grace the boards with a post
I assume you mean v1.2.
But basically, when v1.2 comes out and there's some bug in it they'll get adressed.
v1.2 isn't the end of the line.
Froggy - I know 1.2 isn't the end of the line. I'm more interested in the actual process. Thanks
lol wat does NT mean?
bump bascially
NT = No Text
NT= No text... I didn't mean to bump... replaced it with text
That is a good question pacov.
Can we get an answer please about how things work? Frogboy maybe?
I believe the contract Stardock has with GPG is for a set period of time. Once that magic date hits, GPG is no longer responsible for releasing updates pro bono. I also seem to remember that the DLC for the DGs is a separate part of the agreement.
It's my understanding is that GPG has agreed to provide updates through X date, but SD has to pay for all of the updates. So, that just means that GPG says they will have someone there that can work on the game if needed for pay. But anyway, I really just want to know if I'm understanding the process for patches/QA. If I understand their model correctly, then it makes alot of sense for everyone to have us assist with testing prior to a release going final. We'd get the benefit of trying out new things early, they'd get the benefit of having a much larger unpaid QA team, we'd get to see more fixes to the build before it went live, it might save SD money, and we'd actually feel like the game is ours (which will go a long way once modding is out).
"
I believe the contract Stardock has with GPG is for a set period of time. Once that magic date hits, GPG is no longer responsible for releasing updates pro bono. I also seem to remember that the DLC for the DGs is a separate part of the agreement."
1 year wooo~~~~
a final bump..
I'm curious about the QA and patch creation and release process myself, however it seems that everyone is keeping quiet about it. It would be interesting to know, but I could also see how people who get upset. It's the old truism about liking sausage until you find out what goes in it.
Yeah, the one year date has hit.
Well, since noone else is I will take a crack at this question.
Bear in mind, I am just a content engineer, so I don't deal directly with Stardock and can only comment about what happens at GPG.
Stardock sends us a list of changes they would like to have done. Those changes are handed out to the appropriate people. When those changes ( or at least a bulk of them) are completed, a build is made and sent to Stardock as a WIP build to have Stardock QA take a look at it.
If any bugs or issues are found they contact us back to have further changes/fixes made. It goes back and forth until Stardock QA approves the build.
As for the Stardock QA process or how they decide what goes into each patch, I have no idea.
Hope this at least helps a little.
I think this is what pacov really wanted to ask. and i would like to know about it too. if somebody can answer this, it would be great.
Morpheas is right, but I really appreciate the insight you provided here, Sorian! You answered part of my question at the very least and I do appreciate it. Thanks again for another look behind the scenes and for all of your hard work on Demgod. I really appreciate all of the hard work you are doing for us and all of the fixes you try to cram in. I hope you get a break from Demigod to work on SupCom2 (as it sounds like you'd like to be focussed on just 1 project for awhile). Thanks again!
There are many great features available to you once you register, including:
Sign in or Create Account
