OPENDAYLIGHT CONTRIBUTIONS: PROJECT PROPOSAL TO RELEASE Deepthi V - - PowerPoint PPT Presentation

OPENDAYLIGHT CONTRIBUTIONS:

PROJECT PROPOSAL TO RELEASE

Deepthi V V, Ericsson Vishal Thapar, Ericsson [Inputs From Prem Sankar G, Ericsson]

AGENDA

• Introduction
• Project Lifecycle
• Project Proposal
• Project Release Schedule
• Q&A

OPENDAYLIGHT

• OpenDaylight is a collaborative

project under The Linux Foundation to foster innovation and create an

• pen and transparent approach to

Software-Defined Networking

ODL CONTRIBUTIONS FROM INDIA

PROJECT LIFECYCLE

Schematic View

Mature Release Process

Simultaneous Release

• Follow mature project standards.
• Dependency between projects handed through Offset Projects:
• A project with offset 0 does not depend directly on other projects.
• A project with offset 1 depends on projects with offset 0.
• A project with offset 2 depends on projects with offset 0 and 1, and so

forth

• Milestones are spaced roughly 4 weeks apart taking into account

significant holidays.

• Release Candidates (RC) are spaced 2 weeks apart
• Service Releases are roughly 6 weeks and 12 weeks after the

Formal Lithium Release.

Project Proposal

Proposal Submission Guidelines

• https://wiki.opendaylight.org/view/Project_Proposals:Main
• Prepare wiki for your project:
• Name
• Repo Name
• Description
• Scope
• Presentations
• Resources Committed (developers committed to working)
• Initial Committers
• Vendor Neutral
• Meets Board Policy (including IPR)
• Send mail to project-proposals@lists.opendaylight.org

Creation Review

• 2 weeks after project proposal mail
• Schedule creation review with TSC
• 20-30 mins
• IRC / WebEx
• Present your proposal
• Questions:
• Modules
• Module interaction
• Use cases

Approved Creation Review

• IPR Review for any code that

you bring in

• Phil Robb
• helpdesk@opendaylight.org
• TSC Minutes or approval mail
• For your initial resources
• Project wiki

Checklist

• Git repository
• Jenkins job
• Jenkins silo, setup, verify
• Verify, merge, integration
• Bugzilla entry
• Mailing list - <repo-name>-dev
• Create and subscribe
• Project Main Wiki
• TSC Meetings
• Calls
• Susbcribe to TSC Mailing list
• Read TSC Meeting minutes
• POM File structure
• Best Practices
• Jacoco code coverage

READY.. SET.. GO!!!!

PROJECT RELEASE SCHEDULE

M0

• Open release
• Technical debt clearence

M1

• Declare project participation
• Candidate release plan
• Elected project lead
• Meet M2 requirements
• Cross project API negotiations

M2

• Provisional APIs: New or Modified

Externally Consumable APIs

• Tentative APIs
• Dependency on other projects’ tentative

APIs

• Infra setup as per checklist
• Integration – provide instructions and

requirements

• Documentation – provide instructions and

requirements

M3

• Functionality Freeze
• Karaf feature
• Integration project
• Add your project
• Dialog
• Meetings
• Documentation started
• Identification
• ASCII doc
• Meetings

M4

• API Freeze
• Documentation – Word count of each

relevant .adoc file

• Meet requirements for Maven Central

inclusion

• Integration and System Test – Project must

run simple test on karaf distro with recommended features installed on every code merge and any RC events.

M5

• Code Freeze
• Stable branch
• Bug Fixes
• TSC RC0 announcement

RCs

• RC0
• 4-5 weeks from Code freeze of offset 2 project
• TSC RC-1 announcement
• RC1
• TSC RC2 announcement
• RC2
• Release

RESOURCES

• More information and to join:
• wiki.opendaylight.org
• Keep informed and join the conversation
• IRC: #opendaylight on Freenode
• Open mailing lists: lists.opendaylight.org
• @openDaylightSDN
• #OpenDaylight

Q&A