Mercurial > hg-website

comparison text/workflows.txt @ 123:f67bc89db328

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
workflows: Added plan for the workflow structuring.
author Arne Babenhauserheide <bab@draketo.de>
date Tue, 28 Apr 2009 13:07:25 +0200
parents a5c7422e4e4c
children ac97975760a7
comparison
equal deleted inserted replaced
122:76639683db9b 123:f67bc89db328
6 6
7 It is intended to make it easier for you to create your own workflow. 7 It is intended to make it easier for you to create your own workflow.
8 8
9 To write this page we gathered [real life workflows](wiki - workflows), so every more complex workflow in here has proven itself in real life usage. We begin with basic workflows and then go on to more complex examples. 9 To write this page we gathered [real life workflows](wiki - workflows), so every more complex workflow in here has proven itself in real life usage. We begin with basic workflows and then go on to more complex examples.
10 10
11 The workflows on this page are rather terse to give you a good overview. You can find a longer introduction which shows how to use these workflows in [learning Mercurial in workflows](learning_mercurial_in_workflows). 11 The workflows on this page are rather terse to give you a good overview. You can find a longer introduction which shows basic Mercurial usage compatible with these workflows in [learning Mercurial in workflows](learning_mercurial_in_workflows).
12 12
13 <!--Structure: 13 <!--Structure:
14 * For whom? -> Why? 14 * For whom? -> Why?
15 * What do you need? -> Resources + extensions 15 * What do you need? -> Resources + extensions
16 * Single Developer workflow 16 * Single Developer workflow
25 * Smoothing workflows with extensions -> i.e. shelve before merging. 25 * Smoothing workflows with extensions -> i.e. shelve before merging.
26 26
27 27
28 Workflows: 28 Workflows:
29 29
30 General:
30 * One-off patch submission 31 * One-off patch submission
31 * Lone Developer 32 * Lone Developer + laptop + publish
32 * ... 33 * Simple shared push repository for small trusted teams
34 * Several pull repositories with integrators for security and large teams
35
36 collaborating on features:
37 * Shared repo + named branches and bugzilla for feature development
38 * centralized with attic
39 *
40
41 Dependency tracking:
42 * Dependency tracking
43 * Snapshots
44
45 Special usages
46 * Tiered web development
47 * Offsite working on dynamic websites
48 * automatic trusted group of committers for optionally anonymous repositories
49
50 working with other vcs:
51 * Dealing with CVS
33 52
34 --> 53 -->
35 54
36 == Workflows == 55 == Workflows ==
37 56