🚀 go-pugleaf

On 28/06/2014 9:28 PM, k wrote:
>
> "| || ||| ||||| || |" <|||||||||||||||||||||> wrote in message

>> So pretty much everything changes, again,
>> it will be dejadejavuvu all over again
>> bugged,o.p.,u.p.,ragequitifitisn'tfixed,
>> whatareyoucomplainingabout?Ilikeit,Ihateit,Imissvanilla
>>
>> any bets warrior charge is still broken? :-)
>
> ugh.  I played beta Cata and every bug report I posted was clearly ignored.
> every  single   one.  everything I encountered that was broken was still
> broken in-game when Cata eventually dropped
>
> at that point I decided the whole 'beta tester' concept was more a pr stunt

If a bug report isn't a critical gameplay bug but just scenery, text, 
flavour, it goes onto the pile.
If it gains enough complaints it may get actioned.
Alphas and betas have many versions, tracking a lot [1000's], of 
complaints by version is complex so usually prior version complaints 
just go in the bitbucket.
Only the reporters care or remember.

e.g. not wow, but fairly common..
  3 people sort 30,000 bug reports a day, 200 are serious and get elevated,
  tomorrow , 3 people sort 30,000 bug reports a day, 200 are serious and 
get elevated
  next day, 3 people sort 30,000 bug reports a day, 200 are serious and 
get elevated
...
Many are duplicates, or at least lumped into the pile of the bug the 
reviewers think it belongs in.
At the weekly review 3 urgent bugs and 50 large bugs are discussed,
12 get slated for examination 200,000 minor bug reports for 500 minor 
bugs are just numbers on a list and are never looked at again.
At the end of the alpha/beta version cycle they are 4th decimal point on 
a graph of allocated effort/cost.
Here is where our complains and 1500 others about a typo show on the 
beta graph --->.<---

Here is where our complains and 1500 others about a typo on a release 
show on the graph ---><---

Yeah, reporting is pretty much a waste of time :-)