-
Project Plan
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
None
-
NOT_Integrated (UnManaged)
-
Initial
-
SNAPSHOT_Integrated (Managed)
Distribution is ready to become MSI project as shown below:
Healthy Community:
There are currently 9 committers from 5 different company affiliation. The large number of committers is justified not because the project has very active development but because it has to react quickly in some circumstances, for example when a project breaks the distribution or AR and needs to be removed. Currently there is no blocking or critical bugs in Distribution. Distribution committers sync up every Thu 9AM PST in the common integration call.
Responsiveness:
Int/Dist committers act very promptly when distribution breaks because this kind of breakages block the entire development through the existing distribution-check jobs. Besides that Int/Dist normally satisfies all release milestone requirements in a timely manner fashion.
Active Committers:
We currently have 8 active committers (only 1 listed is not active) in int/dist project:
https://wiki.opendaylight.org/view/Integration/Distribution
TSC Attendance:
Current PTL is TSC member so project representation is guaranteed.
Checkpoints Submitted On-Time:
All deliverables for Oxygen can be seen here:
http://docs.opendaylight.org/en/latest/release-process/milestone-readouts.html
Jobs Required for Managed Projects Running:
All required jobs are in place:
https://jenkins.opendaylight.org/releng/view/distribution/
Only unstable job (CSIT) will be removed along with the only feature provided by distribution (odl-distribution-version) in Fluorine release.
Depend only on Managed Projects:
Hopefully that is the case but distribution has no control in which projects are approved to be Managed.
Documentation
The plan is to eliminate all documentation for odl-distribution-version feature (remove in Flourine) but still update common pages like:
http://docs.opendaylight.org/en/latest/getting-started-guide/installing_opendaylight.html
Release Note will be also created for every release.
CLM
Distribution just assembles other ODL components so any issue in CLM is normally due to other ODL projects.