On 29 June 2015 at 16:55, Bill Fischofer <bill.fischo...@linaro.org> wrote:
> Perhaps we can use the Tuesday ODP Jira planning meeting to also do a > quick review of outstanding patches and their review status (similar to > Thursday's bug meeting)? > We could take time for both, lets try it, but before breaking for the Sprint we started to get some good traction on translating threads and ideas into concrete work items and I hope we continue to do that. I also feel that there is an exception that if a patch is really wanted it will be pushed by its submitter. If it is necessary to "grep" the list to pull things in, then the submitter may not be serious about sticking around to support the idea for very long and I question if we want the patch. > > Again, I think Jenkins would help here, > do you mean Gerrit :-) ? For the API-NEXT work I think that Gerrit helps given the body of contributors who may not follow the lists on a daily basis but who do care about the direction of the API. In that case a central clear list of pending patches is a great asset. > if only as a management tool to track what's outstanding and to assign > review responsibility to those that don't seem to be getting picked up in a > timely manner. > > On Mon, Jun 29, 2015 at 12:26 PM, Mike Holmes <mike.hol...@linaro.org> > wrote: > >> >> >> On 29 June 2015 at 13:20, Maxim Uvarov <maxim.uva...@linaro.org> wrote: >> >>> On 06/29/15 20:13, Mike Holmes wrote: >>> >>>> As soon as we have Christophes test framework migration to platform >>>> calling of the tests in we should consider a point release. >>>> >>>> The rational is the need that the ODP-DPDK implementation has for this >>>> work. >>>> >>>> ODP-DPDK currently has a platform specific limitation when running >>>> "make check" vs running the tests by hand that causes "make check" to >>>> fail. I believe the hugepages used by DPDK need freeing before executing >>>> the next test, Christophes work enables this seamlessly between tests. >>>> >>>> Mike >>>> >>> >>> Yes. Also a lot of patches without any comments. Or they are fine or >>> nobody took a look at them. >>> >> >> We are still an evolving community so it may be a little fuzzy who has an >> interest in what area, but I think we need those people generating patches >> to try and find like minded contributors and have them review the work so >> that we can move more swiftly. >> >> >>> >>> Maxim. >>> >>> -- >>>> Mike Holmes >>>> Technical Manager - Linaro Networking Group >>>> Linaro.org <http://www.linaro.org/>***│ *Open source software for ARM >>>> SoCs >>>> >>>> >>>> >>>> _______________________________________________ >>>> lng-odp mailing list >>>> lng-odp@lists.linaro.org >>>> https://lists.linaro.org/mailman/listinfo/lng-odp >>>> >>> >>> _______________________________________________ >>> lng-odp mailing list >>> lng-odp@lists.linaro.org >>> https://lists.linaro.org/mailman/listinfo/lng-odp >>> >> >> >> >> -- >> Mike Holmes >> Technical Manager - Linaro Networking Group >> Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs >> >> >> >> _______________________________________________ >> lng-odp mailing list >> lng-odp@lists.linaro.org >> https://lists.linaro.org/mailman/listinfo/lng-odp >> >> > -- Mike Holmes Technical Manager - Linaro Networking Group Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs
_______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
