[openfabrics-ewg] How to generate IBED releases using 1.0 branch

[Tziporet Koren]

Hi All,

 

This is my proposal how we should work to generate IBED release based on
1.0 branch.

Note that one purpose of this proposal is also to make sure that the
code that goes into kernel is verified and save the need to merge any
kernel level code in the branch.

 

The model should be this:

 

1.	Any module that is already in the kernel will be taken from the
git tree that is targeted for 2.6.17
(http://www.kernel.org/git/?p=linux/kernel/git/roland/infiniband.git;a=s
ummary)
	This include the following: mthca, ipath (if I understand it
should be in soon), core (all modules), ipoib, srp
2.	Kernel modules that are not in Linux kernel will be taken from
these directories:
	iSER, SDP - from the trunk
	RDS: from SilverStorm contrib directory (till they move it to
the trunk)
3.	All user space code will be taken from the 1.0 branch. I will
send all user space patches that are important for this release. If it's
OK I can also check them in, or ask the maintainers as agreed to do so.
4.	MPI:
	MVAPICH - tarball is provided by Mellanox
	Open MPI - tarball is provided by Cisco
	Both tarballs should be placed in OpenFabrics web site (Need a
location from Matt)
5.	IBED build scripts: We will open a specific directory for IBED
release under the 1.0 branch and all relevant scripts will be places
there.
6.	Back port patches: We will have a back port patches directory
under 1.0 branch.

 

 

I think this module can help us to progress both OpenFabrics and IBED
releases very well and also contribute for the stability of code that is
going to Linux kernel.

 

BTW - when do we go public to OpenFabrics general list?

 

Tziporet

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ewg/attachments/20060329/fb6e18cd/attachment.html>