summaryrefslogtreecommitdiff
path: root/wiki/dev/twigs.md
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-03 21:09:11 -0500
committerOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-03 21:27:41 -0500
commit3ea9f16c84395a7c7a0164a581adaca639590859 (patch)
treea83f53b60cd3f939a9c0b2056655b8370448c8f8 /wiki/dev/twigs.md
parent5032ed5340b3dad92e1817bcc915f64eedd0af6a (diff)
Imported notes about branches/twigs
Diffstat (limited to 'wiki/dev/twigs.md')
-rw-r--r--wiki/dev/twigs.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/wiki/dev/twigs.md b/wiki/dev/twigs.md
new file mode 100644
index 0000000..ebc875c
--- /dev/null
+++ b/wiki/dev/twigs.md
@@ -0,0 +1,24 @@
+# Branches and Twigs
+
+## Twigs
+
+* Relatively short-lived
+* Share the commit policy of their parent branch
+* Gain little value from global names
+* Examples: most "topic branches" are twigs
+
+## Branches
+
+* Relatively long-lived
+* Correspond to differences in commit policy
+* Gain lots of value from global names
+* Examples: git-flow 'master', 'develop', &amp;c; hg 'stable' vs 'default';
+ release branches
+
+## Commit policy
+
+* Decisions like "should every commit pass tests?" and "is rewriting or
+ deleting a commit acceptable?" are, collectively, the policy of a branch
+* Can be very formal or even tool-enforced, or ad-hoc and fluid
+* Shared understanding of commit policy helps get everyone's expectations
+ lined up, easing other SCM-mediated conversations