# HG changeset patch
# User Arne Babenhauserheide <bab@draketo.de>
# Date 1240916845 -7200
# Node ID f67bc89db3288db03798ac8a933a82505d445fc0
# Parent  76639683db9be79d389f4534e894b6208a0d223f
workflows: Added plan for the workflow structuring.

diff -r 76639683db9b -r f67bc89db328 text/workflows.txt
--- a/text/workflows.txt	Tue Apr 28 12:51:39 2009 +0200
+++ b/text/workflows.txt	Tue Apr 28 13:07:25 2009 +0200
@@ -8,7 +8,7 @@
 
 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. 
 
-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). 
+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). 
 
 <!--Structure: 
 * For whom? -> Why?
@@ -27,9 +27,28 @@
 
 Workflows: 
 
+General: 
 * One-off patch submission
-* Lone Developer
-* ... 
+* Lone Developer + laptop + publish
+* Simple shared push repository for small trusted teams
+* Several pull repositories with integrators for security and large teams
+
+collaborating on features: 
+* Shared repo + named branches and bugzilla for feature development
+* centralized with attic
+* 
+
+Dependency tracking: 
+* Dependency tracking
+* Snapshots
+
+Special usages
+* Tiered web development
+* Offsite working on dynamic websites
+* automatic trusted group of committers for optionally anonymous repositories
+
+working with other vcs: 
+* Dealing with CVS
 
 -->