[svnbook] r4694 committed - Translation: Is Subversion the Right Tool? (ongoing)
svnbook at googlecode.com
svnbook at googlecode.com
Thu Feb 27 15:39:59 CST 2014
Revision: 4694
Author: jmfelderhoff at gmx.eu
Date: Thu Feb 27 21:39:39 2014 UTC
Log: Translation: Is Subversion the Right Tool? (ongoing)
http://code.google.com/p/svnbook/source/detail?r=4694
Modified:
/branches/1.7/de/book/ch00-preface.xml
=======================================
--- /branches/1.7/de/book/ch00-preface.xml Thu Feb 27 17:10:25 2014 UTC
+++ /branches/1.7/de/book/ch00-preface.xml Thu Feb 27 21:39:39 2014 UTC
@@ -265,52 +265,66 @@
<para>Zunächst müssen Sie sich entscheiden, ob Versionskontrolle
generell für Ihre Ywecke benötigt wird. Falls Sie alte Datei-
- und Verzeichnisversionen
- aufbewahren, sie eventuell wiedererwecken müssen, und
- Protokolle darüber auswerten möchten, wie sie sich im Lauf der
- Zeit geändert haben, dann kïnnen das
- Versionskontroll-Werkzeuge bewerkstelligen. ist Subversion das
- genau passende
- Werkzeug für Sie. Subversion ist auch geeignet, wenn Sie mit
- mehreren Leuten gemeinsam (üblicherweise über das Netz) an
- Dokumenten arbeiten und verfolgen müssen, wer welche Änderung
- gemacht hat. Deshalb wird Subversion so oft in
- Softwareentwicklungsumgebungen eingesetzt – die Arbeit
- in einem Entwicklerteam ist von Natur aus eine soziale
- Tätigkeit und Subversion vereinfacht die Zusammenarbeit mit
- anderen Programmierern. Natürlich ist die Benutzung von
- Subversion nicht umsonst zu bekommen: es kostet
- administrativen Aufwand. Sie müssen ein Daten-Projektarchiv
- verwalten, das die Informationen und ihre gesamte Geschichte
- speichert, und Sie müssen sich gewissenhaft um
- Sicherheitskopien kümmern. Wenn Sie täglich mit den Daten
- arbeiten, werden Sie sie nicht auf die gleiche Art kopieren,
- verschieben, umbenennen oder löschen können wie gewohnt.
- Stattdessen müssen Sie dafür Subversion verwenden.</para>
+ und Verzeichnisversionen aufbewahren, sie eventuell
+ wiedererwecken müssen, und Protokolle darüber auswerten
+ möchten, wie sie sich im Lauf der Zeit geändert haben, dann
+ können das Versionskontroll-Werkzeuge bewerkstelligen. Wenn
+ Sie mit mehreren Leuten gemeinsam (üblicherweise über das
+ Netz) an Dokumenten arbeiten und verfolgen müssen, wer welche
+ Änderung gemacht hat, dann kann ein Versionskontroll-Werkzeug
+ auch das. Deshalb werden Versionskontroll-Werkzeuge wie
+ Subversion so oft in Software-Entwicklungs-Umgebungen eingesetzt
+ – die Arbeit in einem Entwicklerteam ist von Natur aus
+ eine soziale Tätigkeit bei der Änderungen am Quelltext ständig
+ besprochen, durchgeführt, geprüft und manchmal sogar
+ rückgängig gemacht werden. Versionskontroll-Werkzeuge
+ ermöglichen diese Art der Zusammenarbeit.</para>
<!--
- <para>Assuming you're fine with the extra workflow, you should
- still make sure you're not using Subversion to solve a problem
- that other tools solve better. For example, because
- Subversion replicates data to all the collaborators involved,
- a common misuse is to treat it as a generic distribution
- system. People will sometimes use Subversion to distribute
- huge collections of photos, digital music, or software
- packages. The problem is that this sort of data usually isn't
- changing at all. The collection itself grows over time, but
- the individual files within the collection aren't being
- changed. In this case, using Subversion
- is <quote>overkill.</quote><footnote><para>Or as a friend puts
+ <para>There is cost associated with using version control, too.
+ Unless you can outsource the administration of your version
+ control system to a third-party, you'll have the obvious costs
+ of performing that administration yourself. When working with
+ the data on a daily basis, you won't be able to copy, move,
+ rename, or delete files the way you usually do. Instead,
+ you'll have to do all of those things through the version
+ control system.</para>
+-->
+ <para>Mit der Verwendung von Versionskontrolle sind auch Kosten
+ verbunden. Falls Sie die Verwaltung Ihres
+ Versionskontroll-Systems nicht an Dritte weitergeben können,
+ haben Sie offensichtlich die Kosten der Verwaltung selbst zu
+ tragen. Wenn Sie täglich mit den Daten arbeiten, werden Sie
+ sie nicht auf die gleiche Art kopieren, verschieben,
+ umbenennen oder löschen können wie gewohnt. Stattdessen
+ müssen Sie dafür das Versionskontroll-System verwenden.</para>
+
+<!--
+ <para>Even assuming that you are okay with the cost/benefit
+ tradeoff afforded by a version control system, you shouldn't
+ choose to use one merely because it <emphasis>can</emphasis>
+ do what you want. Consider whether your needs are better
+ addressed by other tools. For example, because Subversion
+ replicates data to all the collaborators involved, a common
+ misuse is to treat it as a generic distribution system.
+ People will sometimes use Subversion to distribute huge
+ collections of photos, digital music, or software packages.
+ The problem is that this sort of data usually isn't changing
+ at all. The collection itself grows over time, but the
+ individual files within the collection aren't being changed.
+ In this case, using Subversion is
+ <quote>overkill.</quote><footnote><para>Or as a friend puts
it, <quote>swatting a fly with a
Buick.</quote></para></footnote> There are simpler tools that
efficiently replicate data <emphasis>without</emphasis> the
overhead of tracking changes, such as <command>rsync</command>
or <command>unison</command>.</para>
-->
- <para>Unter der Annahme, dass Ihnen die zusätzlichen
- Arbeitsabläufe nichts ausmachen, sollten Sie trotzdem sicher
- sein, dass Sie Subversion nicht für die Lösung eines Problems
- verwenden, das andere Werkzeuge besser lösen könnten. Zum
+ <para>Selbst unter der Annahme, dass Sie mit dem
+ Kosten/Nutzen-Verhältnis des Versionskontroll-Systems
+ einverstanden sind, sollten Sie keins verwenden, nur weil es
+ das, was Sie möchten, <emphasis>kann</emphasis>. Erwägen Sie,
+ ob andere Werkzeuge Ihnen eher entgegenkommen können. Zum
Beispiel wird Subversion, weil es die Daten an alle
Beteiligten verteilt, als generisches Verteilsystem
missbraucht. Manchmal wird Subversion zum Verteilen von
@@ -327,7 +341,141 @@
mitzuverfolgen, etwa <command>rsync</command> oder
<command>unison</command>.</para>
- <!-- TODO: Fill in the landscape with respect to DVCS -->
+<!--
+ <para>Once you've decided that you need a version control
+ solution, you'll find no shortage of available options. When
+ Subversion was first designed and released, the predominant
+ methodology of version control was <firstterm>centralized
+ version control</firstterm>—a single remote master
+ storehouse of versioned data with individual users operating
+ locally against shallow copies of that data's version history.
+ Subversion quickly emerged after its initial introduction as
+ the clear leader in this field of version control, earning
+ widespread adoption and supplanting installations of many
+ older version control systems. It continues to hold that
+ prominent position today.</para>
+-->
+ <para>Once you've decided that you need a version control
+ solution, you'll find no shortage of available options. When
+ Subversion was first designed and released, the predominant
+ methodology of version control was <firstterm>centralized
+ version control</firstterm>—a single remote master
+ storehouse of versioned data with individual users operating
+ locally against shallow copies of that data's version history.
+ Subversion quickly emerged after its initial introduction as
+ the clear leader in this field of version control, earning
+ widespread adoption and supplanting installations of many
+ older version control systems. It continues to hold that
+ prominent position today.</para>
+
+<!--
+ <para>Much has changed since that time, though. In the years
+ since the Subversion project began its life, a newer
+ methodology of version control called <firstterm>distributed
+ version control</firstterm> has likewise garnered widespread
+ attention and adoption. Tools such as Git
+ (<ulink url="http://git-scm.com/" />) and Mercurial
+ (<ulink url="http://mercurial.selenic.com/" />) quickly rose
+ to the tops of the distributed version control system (DVCS)
+ ranks. Distributed version control harnesses the growing
+ ubiquity of high-speed network connections and low storage
+ costs to offer an approach which differs from the centralized
+ model in key ways. First and most obvious is the fact that
+ there is no remote, central storehouse of versioned data.
+ Rather, each user keeps and operates against very
+ deep—complete, in a sense—local version history
+ data stores. Collaboration still occurs, but is accomplished
+ by trading <firstterm>changesets</firstterm> (collections of
+ changes made to versioned items) directly between users' local
+ data stores, not via a centralized master data store. In
+ fact, any semblance of a canonical <quote>master</quote>
+ source of a project's versioned data is by convention only, a
+ status attributed by the various collaborators on that
+ project.</para>
+-->
+ <para>Much has changed since that time, though. In the years
+ since the Subversion project began its life, a newer
+ methodology of version control called <firstterm>distributed
+ version control</firstterm> has likewise garnered widespread
+ attention and adoption. Tools such as Git
+ (<ulink url="http://git-scm.com/" />) and Mercurial
+ (<ulink url="http://mercurial.selenic.com/" />) quickly rose
+ to the tops of the distributed version control system (DVCS)
+ ranks. Distributed version control harnesses the growing
+ ubiquity of high-speed network connections and low storage
+ costs to offer an approach which differs from the centralized
+ model in key ways. First and most obvious is the fact that
+ there is no remote, central storehouse of versioned data.
+ Rather, each user keeps and operates against very
+ deep—complete, in a sense—local version history
+ data stores. Collaboration still occurs, but is accomplished
+ by trading <firstterm>changesets</firstterm> (collections of
+ changes made to versioned items) directly between users' local
+ data stores, not via a centralized master data store. In
+ fact, any semblance of a canonical <quote>master</quote>
+ source of a project's versioned data is by convention only, a
+ status attributed by the various collaborators on that
+ project.</para>
+
+<!--
+ <para>There are pros and cons to each version control approach.
+ Perhaps the two biggest benefits delivered by the DVCS tools
+ are incredible performance for day-to-day operations (because
+ the primary data store is locally held) and vastly better
+ support for merging between branches (because merge algorithms
+ serve as the very core of how DVCSes work at all). The
+ downside is that distributed version control is an inherently
+ more complicated model, which can present a non-negligible
+ challenge to comfortable collaboration. Also, DVCS tools do
+ what they do well in part because of a certain degree of
+ control withheld from the user which centalized systems freely
+ offer—the ability to implement path-based access
+ control, the flexibility to update or backdate individual
+ versioned data items, etc. Fortunately, many wise
+ organizations have discovered that this needn't be a religious
+ debate, and that Subversion and a DVCS tool such as Git can be
+ used together harmoniously within the organization, each
+ serving the purposes best suited to the tool.</para>
+-->
+ <para>There are pros and cons to each version control approach.
+ Perhaps the two biggest benefits delivered by the DVCS tools
+ are incredible performance for day-to-day operations (because
+ the primary data store is locally held) and vastly better
+ support for merging between branches (because merge algorithms
+ serve as the very core of how DVCSes work at all). The
+ downside is that distributed version control is an inherently
+ more complicated model, which can present a non-negligible
+ challenge to comfortable collaboration. Also, DVCS tools do
+ what they do well in part because of a certain degree of
+ control withheld from the user which centalized systems freely
+ offer—the ability to implement path-based access
+ control, the flexibility to update or backdate individual
+ versioned data items, etc. Fortunately, many wise
+ organizations have discovered that this needn't be a religious
+ debate, and that Subversion and a DVCS tool such as Git can be
+ used together harmoniously within the organization, each
+ serving the purposes best suited to the tool.</para>
+
+<!--
+ <para>Alas, this book is about Subversion, so we'll not attempt
+ a full comparison of Subversion and other tools. Readers who
+ have the option of choosing their version control system are
+ encouraged to research the available options and make the
+ determination that works best for themselves and their fellow
+ collaborators. And if, after doing so, Subversion is the
+ chosen tool, there's <emphasis>plenty</emphasis> of detailed
+ information about how to use it successfully in the chapters
+ that follow!</para>
+-->
+ <para>Alas, this book is about Subversion, so we'll not attempt
+ a full comparison of Subversion and other tools. Readers who
+ have the option of choosing their version control system are
+ encouraged to research the available options and make the
+ determination that works best for themselves and their fellow
+ collaborators. And if, after doing so, Subversion is the
+ chosen tool, there's <emphasis>plenty</emphasis> of detailed
+ information about how to use it successfully in the chapters
+ that follow!</para>
</sect2>
More information about the svnbook-dev
mailing list