Hi, all

I just think that if we can have some agreements on the DPDK CI tasks firstly, then discuss about the open list.  

Possible agreement parts:

1. Schedule tool: Jenkins.

LF has the Jenkins as the schedule tool. So I wonder if all agree on this schedule tool for scheduling build and regression test.

2. Create per patch check(patchcheck and build) by using Jenkins to trigger

For each patch check, currently we cover the Patchcheck and build.

I noticed Thomas has a separate mail about checkpatch, so does it mean we can remove patchcheck from the build test?

For build test, Intel can provide Intel IA based per patch build report. If there is common format, we can follow it.

3. Create daily or weekly functional/build regression test based on git tree, also using Jenkins to trigger

For the functional/build regression tests, Intel has already sent out the daily build and functional regression test. If there is common format, we can also follow it.

Besides Intel, I have also seen the IBM’s daily build report. Any others want to publish the daily/weekly functional regression tests?

Opens:

1. Centralized or distributed performance lab. Is the decision more dependent on budget or the thoughts?

2. Performance report center. Do you want to publish the performance report and which is the preferred format?  

3. The code review tool is still by mailing list. Is it the final decision?

4. How about the central bug system? Do we want to have one?

Proposal:  Could we have a CI weekly sync-up meeting for discussion only on CI? If most people on the mailing list from EU and PRC, then we could find a more friendly time for PRC people.