Yeah, OK, so the technical definition of a Beta test is that it’s feature complete. But, that’s not how I’ve ever really done it. I consider a Beta a build sent to external testers that’s stable and usable. And, SuperDuper! v2.0 has been in this type of testing since November 22, 2004.
Yeah, that’s right. We’ve had 70 external testers pounding on v2.0 since last November.
The testing has been going great, with very few problems reported, especially considering how much has been changed over the months. And I’m happy to say that we reached an important milestone yesterday: the last new feature of v2.0 was finally released to our external testers. We’re feature complete. Things are working really well.
I feel like I’ve been at sea for a year and have just sighted my first gull. Land can’t be far away!
07 Oct 2005 at 05:54 pm | #
well, i for one can’t wait for this “boat” to beach the shore!
11 Oct 2005 at 02:14 pm | #
By telling us your application has been in beta for almost a whole year, you kinda make us expect a completely bugfree product! Awesome!
11 Oct 2005 at 02:34 pm | #
Completely bugfree? No way—no such thing. We’re just trying to make it as good as we can. Hope you like it.
14 Oct 2005 at 01:05 am | #
You wrote: “...the technical definition of a Beta test is that it’s feature complete.” Maybe the technical definition is, but I’ve worked as a software tester in some big houses and it didn’t quite work out that way there, either. I think that “mostly” or “generally” feature complete might be better phrases!
17 Oct 2005 at 05:08 pm | #
Two suggestions:
Add a ‘mysql dump’ and a ‘subversion repository dump’ item to the scripts menu. If you need an example of the command that needs to be run, let me know and I will hunt it up in the manuals.
Scott
17 Oct 2005 at 05:10 pm | #
Things like that are exactly what the “Before” and “After” script options are for in Advanced, Scott… should work great.
28 Oct 2005 at 12:15 am | #
Dave, you’re the man. And thanks for keeping the communication up on the blog.