From: Date: June 19 2007 10:10pm Subject: Code reviews performed in public List-Archive: http://lists.mysql.com/internals/34759 Message-Id: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323584-2014412870-1182282575=:12869" --8323584-2014412870-1182282575=:12869 Content-Type: TEXT/PLAIN; CHARSET=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Content-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, those of you who are pulling from the BK source trees may have noticed it already: we have slightly updated our post-commit triggers to only send com= mit messages to the public commits@stripped mailing list (instead of sen= ding copies to MySQL-internal mailing lists as well). The change is expected to slowly propagate into the various team trees, so this will be a gradual transition. The intention behind this is to perform code reviews and push approvals via this public commit mailing list instead of doing them in private, as it use= d to be the case so far. By doing so we want to encourage community participation and making our development process more transparent. We also hope to get more and better contributions in the long run, as we expect the contributors to learn from = our review standards applied internally. Potential errors in a patch or glitche= s that were not noticed by a reviewer will also more likely be caught by othe= rs that may be following the review process. Quoting Eric S Raymond: "Given en= ough eyeballs, all bugs are shallow." In the long run, keeping the commits and reviews in one mailing list will a= llow us to better integrate this process with other tools like the Bugs Database= =2E So if you are curious to learn more about how we perform code reviews and w= hat stuff the developers are currently working on, consider joining this list! = You can subscribe to it via http://lists.mysql.com/internals (archives are available from there, too) or by sending an empty email to commits-subscribe@stripped. Some more information about Code reviews and coding guidelines can be found= on the MySQL Forge Wiki as well: http://forge.mysql.com/wiki/Code_Review_Process http://forge.mysql.com/wiki/MySQL_Internals_Coding_Guidelines Thanks! Bye, =09LenZ - --=20 Lenz Grimmer , Community Relations Manager, EMEA MySQL GmbH, http://www.mysql.de/, Radlkoferstr. 2, D-81373 M=C3=BCnchen Gesch=C3=A4ftsf=C3=BChrer: Kaj Arn=C3=B6 - HRB M=C3=BCnchen 162140 http://forge.mysql.com/ | http://planetmysql.org/ | http://dev.mysql.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQFGeDghSVDhKrJykfIRAtttAJ9YuyEowppFIJY7hcMubu4Q2UFAmgCeO4ub LsUkS1/krtGW24rl+VA0Q9w=3D =3DW2+U -----END PGP SIGNATURE----- --8323584-2014412870-1182282575=:12869--