[TSC-54] LISP Flow Mapping moving to Managed Release for Fluorine

Fri, 6 Apr 2018 00:43:32 +0000

Summary

This is a request for the LISP Flow Mapping project to move from Unmanaged to Managed for the first time in the Fluorine release. See below for how each requirement is fulfilled by the project.

Healthy Community

LISP Flow Mapping is part of OpenDaylight since the initial Hydrogen release, and had contributions (code, documentation, bug reports, testing, etc.) from a wide variety of committers and non-committers from different organizations throughout all releases, as reflected by the Git/Gerrit, Bugzilla/JIRA and mailing list history.

Responsiveness

Responsiveness on the project and release email list has been very good, and most committers are also active and can help out interactively on IRC. We monitor JIRA for new issues, notify our downstreams of breaking changes, sometimes even providing patches.

Active Committers

We are currently reviewing our committer list to prune inactive committers, but so far we have had no issues in the timely review of patches.

TSC Attendance

The project currently has a committer on the TSC, but was always following TSC meetings and mailing list before that, and will if we will no longer have a committer as a TSC member.

Checkpoints Submitted On-Time

The LISP Flow Mapping project acknowledges that we're required to submit checkpoints on time, which we will do. We have a long history of providing milestone readouts on time.

Jobs Required for Managed Projects Running

Required jobs for Managed Projects:

Distribution check
Validate autorelease (not created yet for Fluorine)
Merge
Sonar
CLM

Depend only on Managed Projects

The LISP Flow Mapping project depends on the following ODL projects:

odlparent
yangtools
mdsal
netconf
controller
neutron
honeycomb/vbd
dlux

We will encourage our dependencies to become Managed, or remove them as a dependency.

Documentation

We have had a User Guide and Release Notes for each release, and we will continue to maintain and extend them.

CLM

The project acknowledges that we're required to handle Component Lifecycle Violations in a timely manner.

OpenDaylight JIRA