OpenDaylight Helium M3 Report Out Template
|
Phil Robb
Hello Helium Project Contacts and others interested in a solid ODL Helium Release: I would like to remind all of the Project-Primary-Contacts that M3 is next Monday on July 7th, 2014.
The M3 developer irc meeting will be held next Wednesday, July 9th, 2014 at 3:30pm UTC - 8:30am PDT at #opendaylight-meeting. Prior to the developer meeting, all participating projects should update their project plans indicating the status of all deliverables up to and including those designated for M3. For those projects that have not yet done this, please see an example such as the OVSDB Integration project (https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan).
Some folks have started to send out their M3 report-outs, but I would like to suggest that all projects provide clear and specific status on deliverables that should be present as part of M3. Also, if any of the deliverables are not fully, 100% complete please clearly identify that, and indicate a high-confidence future date when the deliverable will be completed. If you are unable to provide a high confidence date due to unresolved dependencies, a lack of resources, etc. please indicate that as well. Those projects late, but with a high-confidence date will be considered "yellow" and the projects with unresolved issues will be considered "Red".
Here is a proposed template for the M3 Report out. If you have suggested alterations please respond with them. If not, please use this template to submit your M3 Report Out, and please send it to release@....
==== <PROJECT NAME> OpenDaylight Helium M3 Status update. Project Release Plan has been updated and is located here: <URL to Project Plan>
M2 Deliverable Status: Final Release Plan Complete: YES/NO Gerrit/Jenkins merge process successfully pushes project binary artifacts to Nexus repo: YES/NO
M3 Deliverable Status: Continuous Integration Test Working: YES/NO Continuous Integration Testing is where your project has a Jenkins job which will rebuld and retest to an appropriate level when a project you depend on publishes new artifacts to the nexus repo.
Project Documentation has started: YES/NO Project Development Status Summary: Please indicate a summary of deliverables completed for M3 and a RED/YELLOW/GREEN indicator regarding your project's overall status. If YELLOW or RED please indicate why and what can or will be done to return the project to a GREEN status.
== End of Template== Thanks, Phil. -- Phil Robb Director - Networking Solutions The Linux Foundation
(O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb |
|
|