little research on recent Version Controll Systems part2
There was some buzz in my head and I took a closer look at the part that I hadn't. Yes it was the Bazaar. I can tell you git is super-fast, and a really good and mature system, but developed for Linux an *nix like systems. Windows is not officially supported, however I can tell you it is really usable. And it has got a disadvantage over Bazaar that cannot correctly follow the renaming of the tree items. Bazaar developed in python because of this that supports windows naively. I am not a windows fun, but if your company is you can't use other systems.
I have two actively developed projects, one of them is on Windows, and the other hacked from Linux and Windows. Both has a smaller team, and we migrated toBbazaar at the development machines and both uses Svn on the server side. On the last mentioned we decided to move to Bazaar completely, and everybody loves it, compared to the Svn in the client side it is really easy to create, and merge branches. It has got several gui-s to manage your bazaar branches, but believe me the command line is still superior, and quite easy to manage your versioning related jobs. I definetly positive about that to if someone migrates from Svn to Bazaar it 'll be fun and not a problem. Some example lines the ones who are still in doubt.
If you are familiar with svn it wont't be a problem
bzr co svn://path_to_your_project
If it is an svn project that won't be a problem for the bazaar too:).
bzr co https:// path_to_your_project
If you stand in a Bazaar repo and you say
bzr commit --local
Yout bazaar will commit your changeset locally, and won't touch the server, if you do it several Times after each other, and someone has commited into the central repo you just say:
bzr update
bzr commit
The magic just happens and your local changes merged with the central repo and your changes ar on the server. Bazaar knows exactly where drom your branch comes from therefor it does not makes conflicts only if it is really needed.
The big big plus that it is working if you are offline too. You have the whole repo with yoursef and ar eble to look back and find something in your older revisions.
I have two actively developed projects, one of them is on Windows, and the other hacked from Linux and Windows. Both has a smaller team, and we migrated toBbazaar at the development machines and both uses Svn on the server side. On the last mentioned we decided to move to Bazaar completely, and everybody loves it, compared to the Svn in the client side it is really easy to create, and merge branches. It has got several gui-s to manage your bazaar branches, but believe me the command line is still superior, and quite easy to manage your versioning related jobs. I definetly positive about that to if someone migrates from Svn to Bazaar it 'll be fun and not a problem. Some example lines the ones who are still in doubt.
If you are familiar with svn it wont't be a problem
bzr co svn://path_to_your_project
If it is an svn project that won't be a problem for the bazaar too:).
bzr co https:// path_to_your_project
If you stand in a Bazaar repo and you say
bzr commit --local
Yout bazaar will commit your changeset locally, and won't touch the server, if you do it several Times after each other, and someone has commited into the central repo you just say:
bzr update
bzr commit
The magic just happens and your local changes merged with the central repo and your changes ar on the server. Bazaar knows exactly where drom your branch comes from therefor it does not makes conflicts only if it is really needed.
The big big plus that it is working if you are offline too. You have the whole repo with yoursef and ar eble to look back and find something in your older revisions.
Comment Form under post in blogger/blogspot