[openfabrics-ewg] IBED-1.0-rc2 build issue - PR# 22 created

[Matters, Todd]

I agree with Tziporet, go back to the trunk.

Todd


______________________
Todd A. Matters
SilverStorm Technologies
(610)233-4809


-----Original Message-----
From: openfabrics-ewg-bounces at openib.org
[mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Tziporet Koren
Sent: Friday, March 17, 2006 12:53 PM
To: Bryan O'Sullivan; Sharma, Karun
Cc: openfabrics-ewg at openib.org
Subject: RE: [openfabrics-ewg] IBED-1.0-rc2 build issue - PR# 22 created

Hi All,

We build RC1 based on the branch, but since the branch was not updated
and there are important bug fixes & small features we moved to build RC2
from the trunk.

Now that a decision was taken on the OpenFabrics EWG we should synch up
and work on one branch.

The problem is that the branch was created when we were in the middle of
development, so there are so many changes we need that it will take a
lot of work to decide which fix should be in and which not.

So I see two options:
1. Review all patches since the branch was taken, and decide for each
one if it's in or out. This task will take a lot of time and sure will
delay the release. And there is also a chance that we will forget some
patch and work later very hard to find it. 

2. Take the branch again now - my preference.
Regarding RPMs: We already have spec files for all packages that are
working with the trunk and also with the branch. So we can gladly
contribute them and there will be no extra work. In this way all will
join 
We also have build machines for most of relevant machines that need to
be supported and backport patches for older kernels.

I am going for one week vacation (sorry for not coordinated with the EWG
forming :-) so I will not be able to participate in the coming week
discussions.
Vlad from Mellanox is the one who prepared all the build, install & spec
files and he will be able to help regarding any technical
issue/question. Also Michael Tsirkin is aware for all the code changes.
Aviram will replace me in all management aspects.

I am sure that we can find the way to collaborate and make this release
a success.

Tziporet


 

-----Original Message-----
From: openfabrics-ewg-bounces at openib.org
[mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Bryan
O'Sullivan
Sent: Friday, March 17, 2006 6:18 PM
To: Sharma, Karun
Cc: openfabrics-ewg at openib.org
Subject: Re: [openfabrics-ewg] IBED-1.0-rc2 build issue - PR# 22 created

On Fri, 2006-03-17 at 09:38 -0500, Sharma, Karun wrote:
> IBED is Mellanox Infiniband Enterpris Distribution which is a part of
> OpenIB.

Hmm.  OK.

As I understand it (and contrary to the note I sent yesterday), the
intention has actually been to not create a separate EWG branch, but to
use the 1.0 branch.  I see that the IBED drop comes off the OpenIB
trunk, which means it is already quite a bit out of sync with the 1.0
branch.

As I've done quite a bit of work to get the 1.0 branch into a shape
where it can build RPM packages that work properly at all, I'd suggest
that Mellanox nominate specific items that are needed from the IBED drop
or from trunk that should get imported into the 1.0 branch, so that we
can converge on a single tree again.  That way, we can keep the testing
and integration load manageable.

	<b

_______________________________________________
openfabrics-ewg mailing list
openfabrics-ewg at openib.org
http://openib.org/mailman/listinfo/openfabrics-ewg
_______________________________________________
openfabrics-ewg mailing list
openfabrics-ewg at openib.org
http://openib.org/mailman/listinfo/openfabrics-ewg