Re: Source Control for VB6
1. Yes, you can. One checks it out while the other gets the latest version of it. When the first checks it back in the other checks it out without getting local version. The user can merge the files or whatnot and then check it back in.
2. Just create two separate projects. One Stable and one Development.
VSS' help file is a good source of its features.
Re: Source Control for VB6
Re: Source Control for VB6
Quote:
Originally Posted by RobDog888
2. Just create two separate projects. One Stable and one Development.
Thats what we did, the problem arises though if something gets fixed in the "stable" version, we didnt see a way for it to trickle down to the dev. version.
Re: Source Control for VB6
Thats a procedural issue. All fixes should be applied to the development version and then update the release version. The release version should not be worked on.
Re: Source Control for VB6
We use the Labeling system in VSS.... when a fix goes in, it gets labeled with the ticket number. Then when we build the release, our system gets the latest lables that are associated with the release (via an in-house system).... then based on the labels, it GETs the properversion for that release.
-tg
PS - fixes should NOT be going into the Stable.... fixes should go into Development... that's more of a process breakdown than a problem with VSS (as RD has noted)