Hi committers, Thanks for trusting me however I think both the existing TSC members and the other nominees are more suitable for this role so I reject my nomination. BR/Luis

Very good point, and one advantage of having early documentation is that this can be tested at the same time of the system test development. I remember that for Hydrogen we were correcting few things

Hi Ed, We can add an entry for system test but before that I would like to know more about the CI milestone: - Are these the JUnit and PAX-EXAM tests executed as part of the build in the verify and me

OK, because integration test is being used for many things, I just wanted to make sure what it was the meaning here. Also before I forget, we should have a milestone for release editions definition an

Hi all, Seen the time we spent last release to figure out what goes to each edition, would it be possible to set something like "Release editions components freeze" by M3 so that we can start automati

Hi TSC members, Carol will stand for Integration in today's call. BR/Luis

I second Giovanni proposal of including people opening bugs. I do not see any better way to account and recognize the testing effort in the community. BR/Luis

Hi Ed, with the same reasoning I could contribute a line of code or a line of documentation and be allowed to vote ;) If the idea here is to restrict the people that can run and vote to those that are

Hi Rochelle, I am forwarding your mail to other people that are not part of integration group. Just one comment from your mail: we do not have 250 projects in ODL (that would be crazy to handle), but

Hi Ed, Thanks for bringing this in as we have got some requests for hosting distributions other than the 3 we know in the integration repository, karaf or toaster are examples of this. I personally th

Another reason (or the main reason) to host an edition in the integration repository is that we can launch system test on it every time is being built.

Yes Chris, I believe we can have folder separation between formal and not formal editions if needed, right Ed? BR/Luis

Hi all, After TSC call today, here is my proposal on how to handle unsupported distributions in the integration repo. This is what we have today for official distributions: /distributions/base /distri

Hi Mathieu, I am not sure I am following you here but it would be good to understand what will be the impact of Karaf in the following items: - Java code and Java testing, this is currently happening

Hi Phil, I will not be at OpenStack Summit but I believe there will be some TSC members and LF people meeting with the Huawei team. BR/Luis

Hi David, On your first wish, we are working in Integration group to get API coverage numbers so that we can use this for release requirements Related to your second wish, we are also working in Integ

Hi Ed, I do not have objection on this way to build the stable branch however we need to clarify what will be the final stable version: <hydrogen-release>-1-SNAPSHOT as originally proposed or <current

Agree with Omar, although it is not perfect, it is the best solution I can think to accommodate both: work on more stable controller and provide a place for new people to contribute with new ideas and

Hi all, Seeing there are no objections here I will start hosting "non-official" distributions under “extra" folder in integration/distributions. BR/Luis

Hi all, Yesterday meeting minutes including performance discussion are available at: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Meetings#Meeting_Minutes BR/Luis