[openfabrics-ewg] [openib-general] Issues regarding release process that were raised in OFED 1.2 plans review

[Nimrod Gindi]

In this case the definition of transfer from Alpha to Beta should be it
is stable (means every one signed that they tested basic tests - and
publish the list of tested items) and Beta is only hardening of the
code.

This is part of what the Task-force recently presented would like to
achieve.
nimrodg

-----Original Message-----
From: Sean Hefty [mailto:mshefty at ichips.intel.com] 
Sent: Wednesday, November 22, 2006 13:45
To: Nimrod Gindi
Cc: Tziporet Koren; EWG; OPENIB
Subject: Re: [openfabrics-ewg] [openib-general] Issues regarding release
process that were raised in OFED 1.2 plans review

Nimrod Gindi wrote:
> In this case we'll be in an open loop.
> In any project there is cut-off date after which features is being
> classified is not fully baked but still enabling the project to move
> forward.

What's required is to define exactly what it means to be alpha and beta 
releases.  I would expect feature freeze to occur before an alpha
release code drop.