[openfabrics-ewg] Re: How to generate IBEDreleasesusing 1.0branch
Matters, Todd
tmatters at silverstorm.com
Wed Apr 5 13:07:38 PDT 2006
But both are sanctioned by OpenFabrics; IBED by the EWG and Release 1.0
directly by the board. With the establishment of the EWG by the
OpenFabrics board the consortium of vendors hardening the stack became
an arm of Open Fabrics. If they're both sanctioned by OpenFabrics I
don't see why both can't, eventually, be a single release process.
In any event, again, I think it's too late to change anything for this
release. And I'm happy with the characterization we've been discussing.
Todd
______________________
Todd A. Matters
SilverStorm Technologies
(610)233-4809
-----Original Message-----
From: Roland Dreier [mailto:rdreier at cisco.com]
Sent: Wednesday, April 05, 2006 2:12 PM
To: Matters, Todd
Cc: Shawn Hansen (shahanse); Matt Leininger; Michael S. Tsirkin;
Openfabrics-ewg at openib.org; Sujal Das
Subject: Re: [openfabrics-ewg] Re: How to generate IBEDreleasesusing
1.0branch
Todd> I hesitate to say this, because it may be more difficult to
Todd> change anything at this point, but it would be preferable,
Todd> from my perspective, to have one release process. This is
Todd> why I asked the question about the sanctioning of IBED.
Todd> Maybe the next release.
I think that trying to have a commercially supportable distribution
come directly from OpenFabrics is both not feasible and actively bad
for OpenFabrics and the industry. Let the free software project focus
on what it does best, and have it produce a release that is targeted
at distributors, who can harden it and get it to customers.
- R.
More information about the ewg
mailing list