My only question, why not use GIT on googlecode? This is another case of fragmentation of the project I think, distinctly unclear where to find what. Wouldn't it make sense to have everything hosted in one central place?
Michael Whapples On 07/05/2014 11:49, Mesar Hameed wrote:
Dear all, In the past we have discussed the possibility of moving away from svn to a decentralized version control system, with a lite branching model to improve our workflow/review process and hopefully the quality of the project code. It will also make it easier for features to be developed in parrallel, and merged once completed. It also allows for organizations with customized tables to easely track the project without major problems. We will be using git, since its a very powerful and commonly known version control system. The code will be hosted on github, http://github.com/liblouis/liblouis For those that are not interested in learning git, github provides a svn to git bridge, so you should be able to access the project with your existing svn client. More on this will follow. To improve our code base, we have decided that no work will be committed to the master branch directly, but will live on a feature branch, until the necessary changes are complete, and has been reviewed by at least one maintainer. If the person doing the work on the feature branch happens to be a maintainer s/he should not merge unless it has been reviewed by another maintainer. Before merging, all existing tests should pass. This hopefully will enable us to provide builds directly from our continuous integration server. Please bare with us for the next few days while we do the necessary changes, and update relevant documentation. we have two websites, 1 static at: http://liblouis.org and a dynamic site, including accessible bug/todo items at: http://issues.liblouis.org If you have uncommitted svn patches we will attempt to help you get them moved across to git if needed. For those of you that have svn commit access to the google code project, this will be withdrawn today so that we don't commit to svn accidentally. The git repo will be updated to include the latest commits, and you should be able to resume your work on your git branch tomorrow. Each branch is prefixed with the name of the person responsible for the work on that branch. The svn repository will be kept as read only and will not be updated with any new code. Sorry for any temporary Upheaval. thanks
For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com
