On Fri, Sep 24, 2010 at 3:01 AM, Ryan Ware <ryan.r.w...@intel.com> wrote:
> > > In the cases which do readily exist for code submissions directly into > MeeGo, the mail list format works exceedingly well. It has worked for > large, dynamic projects for a long period of time and has a track record > that can be predicted and relied upon. No, it's not perfect, but as the > person responsible for ensuring security defects are corrected in a > timely and responsive manner, I think the track record shows that mail > lists find a large percentage of the issues while the other tools > mentioned in this thread don't have a similar extensive track record. > But why to enforce only email review, when there is also a group that is interested in review tools. Review of patches is fine, but a tool like reviewboard provides a complete context of the code change and some nice features of easy commenting. A track record cannot be created unless and the new tool is tried out :) > > Ryan > -- Sateesh > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev >
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
