Why the QA team?
The QA team is essentially a way to coordinate multiple people to test the software before it is released. The team was created in response to a number of problems.
Development team had trouble tracking results and general confusion on "is it safe to release?". With a defined policy and tracking, we can now look at the testing results and know when a specific version has been confirmed to be okay for release.
the TripleA code base is very difficult to modify and repeated releases kept introducing small but extremely significant bugs. Regression testing for any of these is a huge effort, and needs to be done repeatedly as the code base is constantly modified. It's too large of a task for just one or two developers, hence the QA team.
How will we know if the QA team is successful?
The number of major bugs reported by users to github issues will go down and head towards zero
The number of times a release is 'rolled back' will go down and head to zero
Where is the QA team heading?
Still formalizing how we operate, but we're getting pretty close to a stable operating process
Long term try to work with development team to reduce the number of items being hand tested
Short/medium term, formalize testing a bit, a few things are getting through, perhaps a testing check list of all features and cases that need to be checked would be a good start
@RoiEX I'd like to push PBF more so then PBEM because 1. its easier to set up and 2. drives more sense of community (people posting/sharing games). So if we can make sure anywhere we have them as a combined button/tab/header that Forum appears first and swap the order of settings on that screen, I think that would be a good step.
@beelee the latest pre release has had many engine fixes for the server and lobby side since the last stable release. This will not affect or should not affect anyone using stable. But yes I am running it in the lobby myself atm.
@prastle bumped You should have a notification to join a new mod group in your profile and notifications.
@AmericanKnight , @epinikion , @champ73 , @guerrilla_J , @SaskWatch , @Gonz , @warmonger2 , @Ajmdemen , @Imbaked , @lalapalooza
@hepps I would say no on holding off on future re-designs. What I'm proposing is a next step that is almost required before we can do a larger redesign. Most of the changes are in the code. Meanwhile, it's pretty trivial and very easy now to alter the screen and which buttons are where, so I can incorporate feedback on that quite readily : )