Basic questions about CVS
Posted in the CVS Forum
São Paulo, Brazil
#1 Jul 1, 2010
Hello to all.
Me and my fellow developers have just recently been trying to figure out a better way to handle version control. We currently use a software called JEDI wich has a lot of problems, and weve been trying to find out the best replacement for it.
We have been reading about CVS, and it sounds like the better alternative (specially since we work with ZEND), but Im failing to comprehend the "big picture" of how our work methodology would be affected.
I have a hard time understanding the practical side of updating older versions of our software. This is the deal :
- We have an older version of our software, say 1.1
- Our current version is 1.2
- Client complains about bug in 1.1
- We have to create a different working folder for 1.1, checkout/sync all files from 1.1, and make related changes there.
- We commit all changes to 1.1
- If we have to merge the changes to 1.2, we do it manually by checking out/modifiying 1.2
What I cant grasp is the merging and whole-project version management. We cannot realize changes to 1.1 unless we have ALL files checkout/synced from 1.2. So, as we need a different working directory for the older version, we cannot merge things, or even consider 1.2 an evolution of 1.1 (its a whole new project).
Sorry if I sound confused, its because I am. Any help would be appreciated to help me better understand how all of this works.
Add your comments below
|What did these pharmacists learn in school?!||14 hr||Vanzandt||1|
|Is inside as sloppy and unkempt as outside??||Jul 6||DSL||2|
|cvs frontend suck. walgreens is way better (Apr '15)||Jun '16||employee||10|
|cvs hiring process (Feb '13)||Jun '16||lulz||12|
|What it's like to work at CVS||May '16||CoryChass||1|
|My pharmacy manager||May '16||aDRpharmfan||1|
|Walgreen store manager thinking about switching...||May '16||Farmer||3|
Find what you want!
Search CVS Forum Now
Copyright © 2016 Topix LLC