Source Code Management or Revision Control

[javapenguin]

---

What source code management (cvs,subversion,mercurial,clearcase,git .....) are you using? I'm confuse which one is the best.

[cold_fusion]

I use svn (subversion). Simpler and better than cvs. No GUI though.

[josephG]

at work were using CVS through eclipse....
but I haven't tried using others..so dli ko ka compare..pero ms popular gyud cguro ang cvs ky mao may karaan..

[moz_k2]

I use svn (subversion). Simpler and better than cvs. No GUI though.

svn pud ako gamit

install lang ka ug tortoise svn para mas nindot
all commands are available in the windows explorer.
kita dayon nimo unsa ang nausab, nya sayon ra commit ug update.

for IDE's naa napud plug-ins
netbeans and eclipse pa ako nasulayan.
sa visual studio kay naa pud, visual svn ata to.

[psyd_1]

were using svn sa amo project

[MarkCuering]

@javapenguin how many users do you have? How many projects? These tools helps you, but somehow it really difficult to manage. We do have PROCEDURES on the entire project, but it seems these tools may not eventually educate the users. Somebody have to decide with this, plan this effectively, there are FREE tools yet you can’t have the assurance that you will be able to make useful in your team, the same as what other people had done, or cheerfully suggested.

You can post some scenarios or layout in your side regarding your project and your team.

But to help you decide here some of my thoughts:

Regarding GUI side… remember tools that requires a lot of pull down menus, buttons on GUI are not that kind of help… you have to get something that is “SCRIPTABLE” you can quickly automate various task, or otherwise you have to spend some time training for every new user may come or for those who don’t know how to use the system. If you don’t want to yell on them “DON’T HIT THE BUTTON!”


Another thing you should consider is on the side of build process and how the system manage, Integration with other IDE’s such as Visual Studios. Does Microsoft SCC not giving you the solutions you need? How about working on different sites? Or doing some parallel development? Releasing different version of product, or doing different projects under same distributed modules being branch or merge.


And the last thing, Performance under respective platform, we try not to experience again what happened to MSVS.NET on their SCC where performance does not really provide satisfaction. Especially if you have to work around different system.
Again, you really have to take time to consider… it’s not that easy, think about how to build modules? Document them? How many users? Versions? You have to provide soon proper documentations and work procedures; standard forms (not electronic) eg. Request certain modules for changes or testing. Anyway, try them all… but just be careful… don’t do it right away in your production.


If the cost doesn’t matter, then get some technical consultants, and pay something reliable with good support.

[javapenguin]

@MarkCuering

Presently I'm the only programmer but there's the possibility of expansion, so before that happens, it's better to get ready. Thanks for your suggestion.

[javapenguin]

So there are only cvs and subversion users here?

What are the things you like and don't like about the revision control your using?

[MarkCuering]

if it won't cost you some delays in your current job then your safe... but to be honest, it took me around 6 months to use that tools. it was CVS before. although we haven't used that, but me and my group decide that we will try, but only for 1 project.

what made us think actually was the price of the project, would you go to try CVS and take the rist with your 15,000 project? or 500,000 project?

one common problems encountered is when you hit by "Cannot create lock," permission errors, or authorization failures (password forgotten), cannot connect to the server because the ROOT environment variable was changed, or the worst "unable to update" wow greatt... after wholeday of work things just not able to update?

we are so happy for the project that cost cheap that can be done for couple weeks turns to be almost 2 months. well, all of us want to try that time, and CVS before wasnt that good as now...(I hope you won't get some problem looking their documentation).

there are 5-7 members before... we started out just module by module...just as simple as tagging, quick notes for fast-driven project... at the moment, we are using SCM and SDP from UK.

[moz_k2]

So there are only cvs and subversion users here?

What are the things you like and don't like about the revision control your using?

bay try to check here:
Comparison of revision control software - Wikipedia, the free encyclopedia
naa dha lain nga repository controls with their features

ma compare jud na kon asa imo gusto