**Important: i am a site member who has volunteered to help test the new site. I am not an administrator, nor in any other official capacity. I am also not an insider: much of what is going on is as mysterious to me as any of the rest of us amongst regular membership. The following is my opinion based upon my experiences, nothing more.**
AskDrFeeder:
Do you even have dedicated SQA? Version control? Regression testing?
Sonic Purity:
SQA: I know there�s at least one motivated volunteer QA tester (me). You may recall that Hiccupx recruited FF2 beta testers starting months ago. I have no idea if there are 50, 12, 3, or 0 others. I do know that some bugs i found during the FF2 pre-release beta phase were fixed, and that others were deemed necessary to push out until after the public release/switchover (i.e. where we are now). Some of these choices surprised me (the bugs struck me as important to address), but i�m an outsider, with no idea of the constraints, pressures, goals, deadlines, etc. involved.
Version control: as an outside beta tester, i was not exposed to these sorts of internals. My focus is front end HTML/CSS, my area of expertise.
Regression testing: from out here, only FF2 beta vs. regression to the live FF1 site, when they were separate and both running. I did do some regression testing vs. FF1, but validating that FF2 did not break any functional aspect of FF1 didn�t seem to be part of the mandate. I can only hope that this was happening on the back end.
))Sonic((
(former Apple SQA tester)
I'm glad there's some SQA going on!
Is there a version number somewhere for citation by bug reports? I personally would find it very hard to report or fix bugs otherwise.
