Posted: 2005-01-04, 13:29 UTC
You should have used a magnifier and click right between yes and no .CoMiKe wrote: and I haven't answered neither yes nor no?
Page 2 of 2
Posted: 2005-01-04, 13:38 UTC
2Sheepdog
OK, I'll bring a microscope tomorrow and if you fooled me...
OK, I'll bring a microscope tomorrow and if you fooled me...
Posted: 2005-01-04, 14:14 UTC
No luck clicking between both
Anyway, this remembers me a Win9x trick in "Regional Settings", where you must click some places in the world map and a game arises...
Excuse the off-topic...
Anyway, this remembers me a Win9x trick in "Regional Settings", where you must click some places in the world map and a game arises...
Excuse the off-topic...
Posted: 2005-01-09, 21:51 UTC
In common there are different testing phases:
alpha: the functionality is already designed, a roughly working version is available. You want to have early feedback from a handful people on your personal opinion concerning the design or just on some first "go - no go" results.
beta: the functionality is well designed, an almost stable version with maybe some well known, minor glitches is available. You want to have feedback from dedicated people with different skills and platforms on useability and stability. Minor design changes and enhancements are possible.
public beta: the design is now fixed, no known bugs are remaining, even the stability on all feasible combinations of platforms should be tested before a general release.
Some authors skip the public beta and have to ship one or more corrected versions shortly after the general release.
The numbers of builds are the same, at least the naming differs and this is the main point !
Calling your stable version a "public beta" tells everybody, still not to use it in a serious environment without certain caution. The global test has still to be verified !
A "public beta" prior to a general release let you trust in the "general release" status due to successfull global testing.
Just note : even a "public beta" has to be stable to the best of your knowledge ...
alpha: the functionality is already designed, a roughly working version is available. You want to have early feedback from a handful people on your personal opinion concerning the design or just on some first "go - no go" results.
beta: the functionality is well designed, an almost stable version with maybe some well known, minor glitches is available. You want to have feedback from dedicated people with different skills and platforms on useability and stability. Minor design changes and enhancements are possible.
public beta: the design is now fixed, no known bugs are remaining, even the stability on all feasible combinations of platforms should be tested before a general release.
Some authors skip the public beta and have to ship one or more corrected versions shortly after the general release.
The numbers of builds are the same, at least the naming differs and this is the main point !
Calling your stable version a "public beta" tells everybody, still not to use it in a serious environment without certain caution. The global test has still to be verified !
A "public beta" prior to a general release let you trust in the "general release" status due to successfull global testing.
Just note : even a "public beta" has to be stable to the best of your knowledge ...
Posted: 2005-01-17, 12:24 UTC
Posted: 2005-01-17, 15:35 UTC
well, that´s no bug, it´s a feature
but (almost) no one knows it
