distributed version control systems (DVCS) Comparisions
I was reading some blogs about the subject and I wanted to get some feedback on how RTC/Jazz fits into the discussion. The main factor to be classified as a DVCS seems to be the ability to have a local copy of the repository to work offline with. RTC seems to have this ability with the concept of workspaces, right? You could load a project and thus have all the code locally on your machine. It's when you perform a check-in operation that you would have to have a network connection to commit the change set?
So of the products mentioned in the various blogs are Git, Mercurial and Bazaar.
So of the products mentioned in the various blogs are Git, Mercurial and Bazaar.
3 answers
RTC-SCM, like most SCM systems, has a local "file area" that contains
the files that you have downloaded from the repository, so you can make
changes to those files while you are disconnected from the network. But
a DVCS system actually has a local repository that lets you do all SCM
operations while you are disconnected from the network (browse the
history, do checkins/merges/whatever). This is not the case for RTC-SCM
.... the workspace data is stored in the RTC repository, and you must be
connected to that repository to browse the history, do checkins, do
merges, etc.
Cheers,
Geoff
rjcarter wrote:
the files that you have downloaded from the repository, so you can make
changes to those files while you are disconnected from the network. But
a DVCS system actually has a local repository that lets you do all SCM
operations while you are disconnected from the network (browse the
history, do checkins/merges/whatever). This is not the case for RTC-SCM
.... the workspace data is stored in the RTC repository, and you must be
connected to that repository to browse the history, do checkins, do
merges, etc.
Cheers,
Geoff
rjcarter wrote:
I was reading some blogs about the subject and I wanted to get some
feedback on how RTC/Jazz fits into the discussion. The main factor
to be classified as a DVCS seems to be the ability to have a local
copy of the repository to work offline with. RTC seems to have this
ability with the concept of workspaces, right? You could load a
project and thus have all the code locally on your machine. It's
when you perform a check-in operation that you would have to have a
network connection to commit the change set?
So of the products mentioned in the various blogs are Git, Mercurial
and Bazaar.
rjcarter wrote:
We are working to support a distributed SCM workflows. It is a proposed
(but not committed) plan item (62532) for RTC 2.0. You would be able to
run a local server on your machine which would host your Jazz Workspace,
and accept and deliver changes from a stream or workspace on a remote
server.
JohnC
SCM Server
I was reading some blogs about the subject and I wanted to get some
feedback on how RTC/Jazz fits into the discussion. The main factor
to be classified as a DVCS seems to be the ability to have a local
copy of the repository to work offline with. RTC seems to have this
ability with the concept of workspaces, right? You could load a
project and thus have all the code locally on your machine. It's
when you perform a check-in operation that you would have to have a
network connection to commit the change set?
So of the products mentioned in the various blogs are Git, Mercurial
and Bazaar.
We are working to support a distributed SCM workflows. It is a proposed
(but not committed) plan item (62532) for RTC 2.0. You would be able to
run a local server on your machine which would host your Jazz Workspace,
and accept and deliver changes from a stream or workspace on a remote
server.
JohnC
SCM Server
rjcarter wrote:
I was reading some blogs about the subject and I wanted to get some
feedback on how RTC/Jazz fits into the discussion. The main factor
to be classified as a DVCS seems to be the ability to have a local
copy of the repository to work offline with. RTC seems to have this
ability with the concept of workspaces, right? You could load a
project and thus have all the code locally on your machine. It's
when you perform a check-in operation that you would have to have a
network connection to commit the change set?
So of the products mentioned in the various blogs are Git, Mercurial
and Bazaar.
We are working to support a distributed SCM workflows. It is a proposed
(but not committed) plan item (62532) for RTC 2.0. You would be able to
run a local server on your machine which would host your Jazz Workspace,
and accept and deliver changes from a stream or workspace on a remote
server.
JohnC
SCM Server
Is there any new information regarding local server on your machines to address distributed development and improve performance when utilizing RTC via the WAN where bandwidth issues exist?