The meeting summary is also available on the Wiki: https://wiki.openfabrics.org/tiki-index.php?page=Teleconf+01-29-2007
Tziporet Abbreviated minutes / summary * We are going for code freeze at Feb 1. * Alpha1 release will be ready at beginning of next week o There are 3 components that are not yet ready for the code freeze (see details) * Agreed on branching and tagging for the OFED 1.2 (see details) * Approved the way external components will be provided * Decided to have a daily build for the full OFED package Action Items: 1. Tziporet to verify QoS status with OSM 2. Or to review all multicast patches in current build to make sure that all needed changes are in. 3. Each git maintainer: open ofed_1_2 branch till Feb 1. 4. Vlad to have a daily build of the full OFED package 5. Roland to send branch name from which to take libibverbs and libmthca Detailed Minutes * The following components are still under development (to be completed after alpha1): o OSM: QoS and LASH routing o RDS: integration to OFED is ongoing o ipath: driver backport patches are not ready yet * Bonding module will support only SLES10 and RHEL up3 for now. Release tagging and branching: Sources developed in OFA: 1. Each git owner will open a branch with the name ofed_1_2. This branch should be opened on Feb 1. 2. Vlad will open a new directory /pub/ofed_1_2. 3. All ofed_1_2 branches will be cloned to this directory. (Note: libibverbs and libmthca will be cloned from kernel.org for Roland's trees.) 4. Any change that should be included in the next OFED package will be first check-in to the maintainer ofed_1_2 branch. A mail should be sent to Vlad (and cc the list) to pull this change. 5. A tag will be set before any package is build. Tag name convention: ofed_1_2_<version> where version will be the suffix of OFED package (e.g. 1.2-alpha1) 6. OFED release package will be built based on this tag. 7. There will be a build script (as in OFED 1.1) to enable each owner to build the package for testing. 8. A daily build of the OFED package will be provided on the OFA server MPI packages: 1. MPI packages are provided as source RPMs 2. Each MPI owner will have an account on the OFA server and will open a directory named ofed_1_2 3. The SRPM package will be placed in this directory, with version indication in the filename (e.g.ompi-1.2.1-xxx) 4. There will be a file named latest.txt that will contain the package that should be taken in the OFED package External packages: Any other external packages that supplied as SRPs (e.g. bonding) and not source will use the same method as above.
_______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general