I use Git on my development and I find it to be reliable so I wonder what is the reason Automattic choose to use SVN for WordPress?
|
|
More then likely it is personal preference. Some people like the workflow introduced by SVN, and some just don't like the distributed model of Git. Some like the way commits, branches, tags etc are handled in one revision control over another. It could also be that they where using SVN before Git was stable enough and they don't want to go through and switch. Why fix something that isn't broken? I really don't think there is a good answer you are going to get on this board, unless someone from Automattic is here. There isn't a right or wrong answer in picking version control systems. |
||||
|
|
|
WordPress moved to Subversion in 2003. Git (as a project) was started in 2005. Absent Doc Brown's flux capacitor coming to fruition, I think the reasons for SVN over Git are rather obvious. (Hint: they rhyme with "fistory", "finertia" and "forganizational fomentum") |
|||
|
|
|
This question is hard to answer by me (and probably anybody else), because I did not made that decision. So you must ask the person who decided to use subversion for the wordpress project to find out more in specific. I don't know the name of the person who made the decision, so sorry for not being very helpful. |
|||
|
|
