HP3000-L Archives

July 1999, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Joe Geiser <[log in to unmask]>
Reply To:
Date:
Fri, 30 Jul 1999 12:00:17 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
On Friday, July 30, 1999 11:04, [log in to unmask]
writes,
<big snip>

> ------------------------------------------------------------Jo
> e Geiser writes--
> Example:  Microsoft has a defined beta program.  There are
> 250 people who
> receive "Pre Beta" code, then when the beta starts, that
> number can swell to
> 10,000, then successive releases are put out to even more.
> The thing is, we
> have a crash 'n burn here for the pre beta stuff, as sure as
> God made litte
> green apples, something catastrphic will happen.  Nothing
> goes on this laptop
> until it hits Release Canadidate status at the very least.
> ------------------------------------------------------------Jo
> e Geiser writes--
>
> I think what Joe is talking about here is Microsoft's
> alpha/beta test program
> for new release's (let us know if I am wrong)...

Actually, this includes OS and products such as Office.  There is one
Beta team which coordinates all of them.

There are times when a specific patch may be tested - such as
security patches - which are downloadable from Microsoft's site.  If
the problem is not widespread, MS will wait and incorporate a patch
into a Service Pack, but if the problem is severe enough, they will
post a specific patch to address a specific issue.

Cheers,

Joe

ATOM RSS1 RSS2