It seems we see several build failures in the carbon source tree per week. It's clear that most of the build failures occurs due to the fact that not following some best practises. By asking individuals to follow best practices does not seem to work because it's natural to make mistakes.
To avoid this what we need to do this enforce the best practises using tools. The tools are integrated into the source trunk so that each and every commit will be monitored if the commit doesn't satisfies the recommendation/best practises you'll not allow to commit. So you'll not have other option rather than fixing the code to have best practises. If we spend some time on this, that'll save lot of time of the developers. We need to come up with the list of best practises ( code review comments, class/method comments etc..) and a suitable tool(python script or what ever) that can integrate into the source trunk or can run on the code before commit. Rajika
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
