Commits

Anonymous committed 2f2681e

[doc] add good practice section

Comments (0)

Files changed (2)

docs/evolve-good-practice.rst

+-----------------------------------------
+Good pratice for (early) user of evolve
+-----------------------------------------
+
+Avoid instability
+--------------------------------
+
+The less instability you have the less you need to resolve.
+
+Evolve is not yet able to detect and solve every situation. And your mind is
+not ready neither.
+
+Branch as much as possible
+--------------------------------
+
+This is not MQ you are not constrainted to linear history.
+
+Making a branch per independent branch will help you avoiding instability and conflict.
+
+Rewrite you change only
+------------------------------------------------
+
+There is no descent conflict detection and handling right now. rewriting other
+people changeset garantee that you will get conflict. Communicate with you
+fellow developer before trying to touch other people part. (which is a good
+pratice in any case)
+
+Using multiple branch will help you to achieve this goal.
+
+Prefer pushing unstability than touching other people changeset
+------------------------------------------------------------------
+
+
+If you have children changeset from other people that you don't really care
+about, prefer not altering them that risking a conflict by stabilizing them.
+
+
+Do not get too confident
+---------------------------
+
+This is an experimental extension and a complexe concept. This is beautiful,
+powerful and robust on paper. But the tool and your mind may not be prepared to
+all situation yet.
    :maxdepth: 1
 
    tutorials/tutorial
+   evolve-good-practice
    evolve-faq
    from-mq
    evolve-collaboration
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.