Summarize past mailing list discussions on patch management issues.
completed by: Clark
mentors: Richard Nyhus
Read all appropriate mailing list discussions on Patch Management issues and summarise the positives and negatives of all the revision control software solutions that were given.
This task will require you to obtain a very basic understanding of what revision control software is. You will also need to gain an very basic understanding of the differences between the more popular revision control software such as Subversion, Mercurial, Git and Bazaar.
You will need to search the Haiku mailing lists for relevant discussions on this topic. However there are links to some of the more important discussions in the links section below.
The revision control software is an integral part of the development of the project. Some of the core developers have started their discontent with Subversion, which is the currant solution. It is therefore very important that all the information is laid out in a clear and concise manner when the core developers make their decision.
You will need a understanding of English that allows you to understand some more technical language that might be used; but you would not be reading this if you did not have this skill already.
If you are more adventurous you could also conclude with your own recommendations.
http://www.freelists.org/post/haiku-development/Patch-format-was-Commitaccess-for-Matt-Madia
http://www.freelists.org/post/haiku-development/Mercurial-was-Patch-format
http://www.freelists.org/post/haiku-development/Git-wasMercurial-was-Patch-format
http://www.freelists.org/post/haiku-development/Mercurial,4
http://www.freelists.org/post/haiku-development/merge-branch
http://www.freelists.org/post/haiku-development/Proposal-Moving-away-from-Subversion
http://www.freelists.org/post/haiku-development/Moving-away-from-Subversion-pt-2
http://www.freelists.org/post/haiku-development/Moving-away-from-Subversion-pt-3