Thanks sandeep. Is labeling same as the version nos that are maintined in the archives. what do you mean by
""For each release first create a new lable and apply it to all source code. (say lable_version1.0_c1)
Then start changes for that release.""
Do we change lables once the object is check in from PB??
You mentioned that we may have problem if something goes wrong when you merge code to test and production env from dev env. There are chances that changes are there in dev env and test env but not in prod env.
But we will only be using test and prod env for creating exe not to change code.
Is there any other way of doing this other than labeling or creating three separate projects for dev, test and prod.
Main Topics
Browse All Topics





by: sandeep_patelPosted on 2008-09-07 at 13:59:34ID: 22412845
I don't recommend to create separate env. You may have problem if something goes wrong when you merge code to test and production env from dev env. There are chances that changes are there in dev env and test env but not in prod env.
...c3..... then..cn)
Hope there must be a labeling facility in your version control system like others. Better use it...
For Example...
1. For each release first create a new lable and apply it to all source code. (say lable_version1.0_c1)
2. Then start changes for that release.
3. Whenever there is a need for testing, apply another lable (say lable_version1.0_c2...then
4. Now once it is tested OK, apply final lable (say lable_version1.0_final)
5. Ask the person who is creating prod exe to get latest only from (lable_version1.0_final)
Even this approach will be easy for you whenever you want source code for previous release.
Hope this will help you.
Regards,
Sandeep