1 / 10

Open MPI Development Process and Beyond: Discussing Goals and Processes

Join this meeting to get an overview of Open MPI development, discuss and agree on processes, and document them. Learn about the technical roles, release management, conflict resolution, and more. Explore the release criteria, testing matrix, and customer guarantees.

jonathanroy
Download Presentation

Open MPI Development Process and Beyond: Discussing Goals and Processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OFED 1.x Processand Beyond Jeff Squyres

  2. Goals • Overview of Open MPI development • DISCUSS -- not just information broadcast • This meeting starts the discussion • Agree on what the processes are • Document the processes • Publish the processes

  3. Open MPI • Similar to OFA • Multiple organizations • Open source • Common releases • Consensus driven • Separate administrative and technical issues

  4. Open MPI • Technical roles • Developers • Release managers: determine when a release is made, what patches go in, etc. • Gatekeepers: minions of the RM’s that do the technical work • Administrative group • Only invoked upon demand • Legal, marketing, etc. • Conflict resolution

  5. Open MPI development • Single code SVN • Development occurs at the trunk -- free for all • Stable release branches, all commits are reviewed and approved • Frequent temporary branches for destabilization work • Bug tracking, milestones, wiki: Trac • Open a ticket for everything • Release managers prioritize and decide what go into each release / milestone • Frequent communication • Weekly developer teleconferences, e-mails, IM • Do not rely on e-mail for archived information: SVN, web site, etc.

  6. Open MPI releases • Release meeting at the beginning of a series • Determine feature set • Determine priorities of each priority (e.g., 1-5 scale, 5 = “blocker” meaning if not complete/fixed, holds up the release) • Determine the schedule • Estimate how long each feature takes, make a plan • Create milestones for when to drop testable pre-releases

  7. Processes to discuss • What are the features of a release? • Who decides / how do we decide? • What are the phases of the release? • What is the exact schedule? • Who decides / how do we decide? • What levels of changes are acceptable at each phase? • How big / little / when / where / etc.? • What is the flow from OFA development to release? • How does one submit a patch? • How do we decide what version of what goes into OFED?

  8. Processes to discuss • What is the release criteria for a release? • How do we decide? • What is the testing matrix? • Who is testing what? • What guarantees are we providing to the customer?

  9. You talk now

  10. OFA

More Related