Re: New project proposal for OpenDaylight: Boron Offset 2 titled "Centennial"
Dear Colin, Anil,
Could you please help answer the questions below. Or we can have a call with one of you for a better understanding.
From: Vishwanath Edavayyanamath (COMMS-EGM)
Sent: Friday, August 5, 2016 9:15 PM
To: 'Colin Dixon' <colin@...>
Cc: Anil Vishnoi <vishnoianil@...>; Karsten Block (Wipro Retail - Germany ) <karsten.block@...>; tsc@...; project-proposals@...; Basavaraj Shivsharnappa Hirapur (Global Media) <basavaraj.hirapur@...>
Subject: RE: [Project-proposals] New project proposal for OpenDaylight: Boron Offset 2 titled "Centennial"
Based on your two points below, I have following questions,
1. Are you saying a project can be proposed any time and once approved by TSC, can be integrated into any specific stable ODL release of our choice? But what rules and process apply to accept the code for these projects proposed outside of a formal release? Do these projects have to follow the same rigorous processes that is being followed in the projects that are part of a formal releases like Boron/Carbon?
2. We don’t necessarily want our code artifacts to be part of the zip file on the downloads page, but just make it available to the respective vendor and Telco community (Wireless Transport) by way of building an ODL distro with specific project packages for the target requirement will suffice.
All we want to know is, if TSC imposes the same rigorous release processes that is followed, if we propose projects which are not part of the formal release? We want to contribute/integrate quickly into a stable Release (like Boron) and check everything works fine and then think later for contributing the project to a formal release like Carbon if it makes sense to be part of the zip file on the downloads page.
From: Colin Dixon [mailto:colin@...]
** This mail has been sent from an external source **
I agree with Anil, it's too late to join the Boron release and I agree, we won't add new projects to the stability releases of older releases.
That being said, here's a few things:
1.) When you have a project proposal it's to be part of the OpenDaylight Foundation's collection of projects, not join a particular release.
2.) Nothing is stopping you from releasing code (and even creating branches) that is designed to work with Beryllium and Boron, just they won't be part of the zip file on the downloads page.