vishwanath.edavayyanamath@...
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.
Regards
Vishwa
toggle quoted message
Show quoted text
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"
Importance: High
Dear Colin,
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.
Regards
Vishwa
** 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.
--Colin
On Tue, Aug 2, 2016 at 11:04 PM, <vishwanath.edavayyanamath@...> wrote:
Dear Anil, Colin,
If it is not possible to contribute new project code artifacts into Boron Release, then would the only
option left for us is to make this project proposal and code contribution in the
Carbon Release of ODL?
Please suggest so that we can start planning accordingly.
Regards
Vishwa
** This mail has been sent from an external source **
As per my understanding new projects are not allowed to back port their code in stable/releases. Stable/release are mainly for the bug fixing only. There was case where new project
did this, but the new project was split from an existing project and it's code was part of the already release version. They did it to avoid maintenance overhead for the new project.
So as per my understanding of the project life cycle it's not allowed to new project to be part of previous releases, but i would defer it to Colin/other tsc members to give you
a concrete answer on it.
On Mon, Aug 1, 2016 at 10:39 AM, <vishwanath.edavayyanamath@...> wrote:
Dear Anil & Team,
I am coming back to check on this thread since, Boron release is around the corner next month and if
there is a possibility for us to propose our Microwave Project and its code artifacts which were delivered as part of ONF Wireless Transport PoC-2 (and would continue its development in PoC-3). We will do a gap analysis of what already exists in Boron and
make a proposal to integrate only those software bundles/components which do not already exist and are unique to the ONF Wireless Transport PoC-2. Our idea is to get the delta code into the formal ODL distro.
We had earlier backed out from this proposal since, we had made this proposition at M4 stage had not
much time left to get our code in. We wanted to attempt this integration after the Formal Release of Boron in Sept. 2016 and attempt to get our code artifacts in one of the service releases of Boron.
Could you please revert if we can make project propositions and still be able to get our code artifacts
into the Service Releases of Boron. If so, can you please elaborate on the process and suggest us some timelines for the same.
** This mail has been sent from an external source **
Thanks for letting us know.
Just want to clarify that approval of the project does not really mean that it will be part of the current official release. For the project those are proposed late in the cycle,
TSC has to take two decision (1) Accepting the project in ODL (2) If requested, allowing project to join the current release given that it's proposed after M1. So you can always propose a project but defer from joining the current release.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended
recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this
email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
_______________________________________________
project-proposals mailing list
project-proposals@...
https://lists.opendaylight.org/mailman/listinfo/project-proposals
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should
not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments
for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
|
