Our group is small. When we first started out, we decided the exclusive checkout model was easier for us to deal with. It's become part of our 'culture' now. We do use branching, but it tends to be a 'whole product' kind of thing. When a version is released to manufacturing, we create a branch for maintenance purposes. It becomes a separate development path for the software. Usually there are only a few updates in the branch, but we've occasionally had active branches that were maintained for years (stern looks at certain customers who refuse to update to later versions).
Not really programming in high level last time, but when... I use to do backups each day with timestamp in name and a tiny explanation on what was going on that day. If I need more explanation then I add a tiny *.txt with what I need to save.
If I come back to high level end, I suppose I will have a look to those tools and pick one.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Well, Git can be confusing and not easy to handle on multiple platforms. But you will try Mercurial only once and fall in love. The TortoiseHg makes your projects so much more transparent and the Gui is the same on all platforms. Even the command line interface is so much easier to learn. Try it out (and choose for yourself, this is my opinion, no need for a war).
And then there are the SVN and Git etc. plugins, so you can first try it out and convert your repositories later ... but stop, I am getting carried away now. If you have a look at it, you may cause even more people to have a look at it and fall in love, so it will be automatically be more widely adopted.
Last Visit: 31-Dec-99 19:00 Last Update: 8-Dec-21 2:22