RE: recomendations for creating a beta with date to expire
RE: recomendations for creating a beta with date to expire
- Subject: RE: recomendations for creating a beta with date to expire
- From: Shawn Bakhtiar <email@hidden>
- Date: Tue, 16 Aug 2011 12:00:56 -0400
- Importance: Normal
Working for a small company, alot of time beta, nay even alpha, products go straight into production.
The conversation goes something like this:
Developer - "Hi everyone, to address our inventory issues, I created a program that ...."
User - "Lets take a look"
User - " Oh my God, this is exactly what we have been looking for, Thanks we'll use it!"
At this point, no matter how much you try to convince them that the application is only an alpha or beta test product, they are going to start using it in production. If that application crashes, and they can restart it, that's one thing. Missing a piece of code to give them better detail, that is another thing. If the app date deceases, and they can not use it again, until you decide, find yourself another job.
Ideal conditions are created in a lab, but in the real world, there is no such thing as ideal conditions. Trying to create controls, you only create more problems.
> From: email@hidden
> Date: Mon, 15 Aug 2011 13:00:34 -0500
> To: email@hidden
> CC: email@hidden
> Subject: Re: recomendations for creating a beta with date to expire
>
> On Aug 15, 2011, at 10:09 AM, Scott Ribe wrote:
>
> > Yes, good point. The expiration date should be just to make sure that the next release has actually gotten installed--and I suspect that's what he meant, getting reports about bugs in old versions after newer ones have been received...
>
> If I were testing something, and found a bug in an older build, the first thing I’d do before reporting it would be to see if I could reproduce it in the newer build. If the build I had was old enough to expire, doubly so. What’s the point of wasting a developer’s time with an issue he or she already fixed six months ago?
>
> Charles_______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden