Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Who is working on MySQL 5.7?
+5 Vote Up -0 Vote Down

First I find out the first commit that is in 5.7 that isn’t in 5.6 (using bzr missing) and then look at the authors of all of those commits. Measuring the number of commits is a really poor metric as it does not measure the complexity of the code committed, and if your workflow is to revise a patchset before committing, you get much fewer commits than if you commit 10 times a day.

There are a good number of people who are committing a lot of code to the latest MySQL development tree. (Sorry for the annoying layout of “count. number-of-commits name”)

  • 1022 Magnus Blaudd
  • 723 Jonas Oreland
  • 329 Marko Mäkelä
  • 286 Krunal Bauskar
  • 230 Tor Didriksen
  • 218 John David Duncan
  • 205 Vasil Dimov
  • 197 Sunny Bains
  • 166 Ole John Aske
  • 141 Marc Alff
  • 141 Frazer Clement
  • 140 Jimmy Yang
  • 131 Joerg Bruehe
  • 129 Jon Olav Hauglid
  • 125 Annamalai Gurusami
  • 106 Martin Skold
  • 104 Nuno Carvalho
  • 103 Georgi Kodinov
  • 102 Pekka Nousiainen
  • There’s also a good number who have 50-100 commits:

  • 99 Mauritz Sundell
  • 97 Bjorn Munch
  • 92 Craig L Russell
  • 85 Andrei Elkin
  • 81 Mattias Jonsson
  • 73 Nirbhay Choubey
  • 71 Roy Lyseng
  • 68 Kevin Lewis
  • 66 Rohit Kalhans
  • 65 Guilhem Bichot
  • 61 Sayantan Dutta
  • 59 Akhila Maddukuri
  • 58 Jorgen Loland
  • 57 Martin Zaun
  • 56 Harin Vadodaria
  • 55 Inaam Rana
  • 53 Venkatesh Duggirala
  • 53 Venkata Sidagam
  • 52 Gleb Shchepa
  • 51 Norvald H. Ryeng
  • 51 Jan Wedvik
  • 50 Tatjana Azundris Nuernberg
  • And there’s even more with less than 50:

  • 49 Manish Kumar
  • 49 Alexander Barkov
  • 48 Shivji Kumar Jha
  • 48 Martin Hansson
  • 42 Maitrayi Sabaratnam
  • 40 Satya Bodapati
  • 39 Horst Hunger
  • 38 Neeraj Bisht
  • 34 Yasufumi Kinoshita
  • 34 prabakaran thirumalai
  • 34 Kristofer Pettersson
  • 33 Evgeny Potemkin
  • 33 Dmitry Lenev
  • 33 Chaithra Gopalareddy
  • 33 Alexander Nozdrin
  • 31 Hemant Kumar
  • 31 Allen lai
  • 31 Aditya A
  • 30 Nisha Gopalakrishnan
  • 30 Anirudh Mangipudi
  • 29 Tanjot Uppal
  • 28 Christopher Powers
  • 27 Sujatha Sivakumar
  • 27 Ashish Agarwal
  • 25 Olav Sandstaa
  • 25 Mayank Prasad
  • 24 Anitha Gopi
  • 24 Ahmad Abdullateef
  • 23 Hery Ramilison
  • 22 Vamsikrishna Bhagi
  • 22 Praveenkumar Hulakund
  • 22 Pedro Gomes
  • 20 Sergey Glukhov
  • 20 Libing Song
  • 19 Vinay Fisrekar
  • 19 Harin Vadodaria
  • 18 Raghav Kapoor
  • 18 Luis Soares
  • 18 Gopal Shankar
  • 18 Astha Pareek
  • 17 viswanatham gudipati
  • 17 Thayumanavar
  • 17 Ramil Kalimullin
  • 16 Oystein Grovlen
  • 15 Dmitry Shulga
  • 15 Amit Bhattacharya
  • 15 Akhil Mohan
  • 14 Ravinder Thakur
  • 14 Kent Boortz
  • 13 Bernd Ocklin
  • 12 Bill Qu
  • 11 Shaohua Wang
  • 10 Sven Sandberg
  • There’s also a good number with fewer than 10 (31 names actually), which is encouraging as it means that this means it’s likely people who are not involved every day in development of new code (maybe QA, build etc) which probably means that (at least internally) contributing code isn’t really a big problem (and as I’ve shown previously, the barriers to external contributions between Oracle MySQL and MariaDB appear to result in roughly the same amount of code from people outside those companies).

    There are 125 names here in total, with 19 having over 100 commits, 22 with 50-100 commits, another 53 with 10-50 commits and 31 with <10. So it’s possible to say that there are at least 125 people at Oracle working on MySQL – and I know there are awesome people who are missing from this list as their work doesn’t result in committing code directly to the tree.

    Votes:

    You must be logged in with a MySQL account to vote on Planet MySQL entries. More information on PlanetMySQL voting.

    Planet MySQL © 1995, 2014, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

    Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.