Is it possible with Remote VSS Server
Uzair
is this that there are two teams connected with a remote VSS server through
VPN on same project, now what is happening is this that we both suffer a lot
in activities like checkin and check out, it takes time, okey, what I want is
something like this that.
when i checkout, it must check out files on remote server
but when i checkin file, i must have two options,
either to checkin on remote server, or checkin files to somewhere local as a
copy , so that, when any member of my team need an updated file, he may get
it from local, or i dont want to stuck with cheking in on each time at my
remote server
Or
I can chekin file to remote server at the end of the day, as I feel my work
done is at some stable state, thus can be chekin to the origonal source
Thus I want something like two repositories, 1 on my local , and second on
my remote server, as a team, working on some module that is somewhat in only
use of my team, i dont want to checkin it on remote server all time.rather i
want to checkin it on local and at the end of day, i want to check in to
remote.
is this possible, or something like this
Jeff Clausius
What if you used two paths:
$/dev/mainproject/
$/dev/mainproject_stable/
where $/dev/mainproject_stable/ was created by using branch/share of
$/dev/mainproject/. Everyone works out of $/dev/mainproject/. Keep
track of things with labels $/dev/mainproject/, and when you are ready,
go ahead and merge the branches applying changes over to
$/dev/mainproject_stable/ when you are ready.
HTH
Jeff Clausius
SourceGear
Are you wanting a fresh new look for VSS? The "Ribbon" awaits. -
http://www.sourcegear.com/sos
Uzair
I want to know one thing, in scenario you suggested,
where $/dev/mainproject/ will be, on somewhere local or remote.
I want it on somewhere local,
If i could not clear my problem,then here it is ,
Infact, I want 2 repositories of my data. One on somewhere local and other
on remote,
why I want this, because my team is working on a module, and no other team
is working on that module ,so its not needed to checkin changes to remote
server all the time, but it do needed to be checked in somewhere( on local
server) so that other members of team can get updated stuff, Thus i want so,
thanx
"Jeff Clausius" wrote:
> .
>
Jeff Clausius
If the SAME set of files but with different changes will be used (think
common libraries or common files for images, utilities, etc.), then the
EASIEST thing to do is keep everything in the SAME VSS database. This
way you can use VSS to do the merge of changes for you.
If there is nothing common or shared between your two types of projects,
then keep a LOCAL version to be shared amongst that team, and when
ready, just ADD the files to the REMOTE VSS database.
If you WILL be sharing files among two different projects and CHANGES
can be made in one or the other project, then the path of least
resistance is to keep everything in the same VSS database. Keeping
track of changes across TWO different VSS database is possible, but can
be very tedious as well as frustrating.
Jeff