In reply to Finish What We Started or Move On

Andrew Boon•6th of June 2011•to kumpleto

That's how development works. You gather up bug reports and release a "Stable" version with fixes. Then you gather up a new bunch. Same for any software. Every now and then, if new features are introduced, a major revision is released.

Permalink•Reply•Plus•0 pluses

DosDawg•7th of June 2011•to Andrew Boon

actually you are supposed to test what you have written prior to releasing. having knowledgeable and understanding beta-testers go through the functionality, to check for performance as well as functionality based on documentation of what each entity is supposed to do.

so hopefully with the idea of Dolphin 8, there will be a different outlook all the way around, starting with documentation.

Permalink•Reply•Plus•1 pluses

SkyForum•13th of June 2011•to Andrew Boon

Really? I hate to say this but you are wrong. Well, that is unless you have the resources Microsoft has to approach products that way. Do you?

Permalink•Reply•Plus•0 pluses

sonnarinternet•13th of June 2011•to SkyForum

Actually, when I develop code, I normally try to test it, and get it as error free as possible. (Alpha Testing), then I hand it off to the owners of the Company (non-programmers) to test extremely thoroughly (Beta Testing), *THEN* we release it. Bugs will still get through occasionally, but a lot less than the "OK, code's done, let's release it!" approach.

We don't have a large staff (Between 3-5 people), but we take the time to test things thoroughly. So you *DON'T* have to have Microsoft's see more

Permalink•Reply•Plus•0 pluses

Blogs

Help

Product

Company