Firstly, Happy New Year to all of you that I have not yet caught up with since returning from the Christmas and New Year break. It has been a busy few weeks since we started back and my lack of blog postings is far from an indication that things are quiet – in fact I have just been too busy with work and personal things to spend time writing blog postings.
No excuse I know and Revelations newsletter that hit my inbox overnight was a welcome poke to get back on here. So, today’s posting is directly from the January 2014 newsletter:
OpenInsight Git is an interface from OpenInsight to the Git source code management system. It will be included in OpenInsight 10.0.
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
You can read more about Git on its web site at HTTP://WWW.GIT-SCM.COM.
For many, source code management is a black art reserved for large corporations who have hundreds of developers. You may think that source code management systems are complicated, involve many steps that have nothing to do with writing code and generally get in the way of being productive. And, for the most part, you would be right.
OpenInsight Git has been designed to be as painless and transparent as possible. There are rules that you will need to follow, but for the most part there are many benefits to using source code management software such as:
- Backup of your source code
- Version Control
- Change Control
- Collaboration with developers remote to your location
OpenInsight Git has been designed to integrate OpenInsight’s development tools with the Git source code management software (SCM). However,there is no reason why OpenInsight Git cannot work with other SCM’s such as Subversion or Mercurial.
OpenInsight Git’s philosophy is simple; it mirrors your OpenInsight source code, stored procedures, windows, messages, help etc. as text files in windows directories. From there, your chosen source code management system does the rest.
Most of you will only use a fraction of the features that Git or any SCM offers. And that’s ok. The important thing is to start using an SCM as soon as possible. From a one man developer to a team of tens or hundreds of developers, using an SCM should become part of your daily work routine.