You want the truth Drak?
You know why there was a "Public Alpha" where everyone could get ahold of it? Because people were whining and moaning that Decal was taking way too long to complete, so you caved into "public pressure" and released a "Public Alpha" and then made all the disclaimers saying "Use at own risk, we ain't gonna help you if we don't want to, etc" ... which is FINE.
Then you guys threw a hissy fit (you know you guys are getting good at that, first when Turbine changed the ToS about Macros, now the latest ones), and said "No more support on vnboards (which is fine, provide official support on your own boards, but PLEASE don't come here and tell people what to do, it just makes you appear "power hungry"

and then YOU go off and say "stop using Alpha 3, use Alpha 4, because we don't need people testing Alpha 3 because we are about to release Alpha 5 and bugs were fixed in Alpha 4. Fine, that is logical, for your TESTERS and Devs, but not for those of us who you "abandoned" to use what you PUBLICALLY RELEASED (you know, just like the words on the Decal Site say .. PUBLIC ALPHA).
Basically, you guys aren't happy with anything.
So, here are my suggestions:
1) If you want to only provide support on your own board, fine. But don't come here and tell people to shut up when people are helping other "end users" out because you won't. If they want "official support", they know where to go.
2) If you want people to test "Alpha 4", that is fine too. Recruit people to do it. I'd suggest on your own board.
3) If you don't want people using Alpha 3, then disable it. You put that feature in the software. You can't just do #4, because the cat is already out of the bag.
4) Put a password on your site and only allow "testers" to use the Alphas. You guys wanted "complete control", that is why you moved support and information to your own site. Spend 30 seconds and set up a password on the release. But we know that won't happen, because the "masses" would hate that, and even fewer people would actually test your software.
5) Stop reading threads like this if you are not going to provide support. It only frustrates you and annoys others.
Again, those are my suggestions, use them as you will.
Have a nice day.
P.S.
Drakier posted:
What Arch_Magi has been saying is MISINFORMATION.
Yeah, right.
Sell that one to someone who is buying it. People here know what the meaning of the word "Alpha" is, and what "Beta" is. You claim that is why you keep posting, to "correct me". Sorry, not buying it.
Alpha, Beta, and Gamma testing
In software development, testing is usually required before release to the general public. This phase of development is known as the alpha phase. Testing during this phase is known as alpha testing.
In the first phase of alpha testing, developers test the software using white box techniques. Additional inspection is then performed using black box or grey box techniques. This is usually done by a dedicated testing team. This is often known as the second stage of alpha testing.
Once the alpha phase is complete, development enters the beta phase. Versions of the software, known as beta-versions, are released to a limited audience outside of the company. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta-versions are made available to the open public to increase the feedback field to a maximal number of future users.
Testing during the beta phase, informally called 'beta testing, is generally constrained to black box techniques although a core of test engineers are likely to continue with white box testing in parallel to the beta tests. Thus the term beta test can refer to the stage of the software—closer to release than being "in alpha"—or it can refer to the particular group and process being done at that stage. So a tester might be continuing to work in white box testing while the software is "in beta" (a stage) but he or she would then not be part of "the beta test" (group/activity).