HACKING: rewindable branches should live in the 'experimental/*' namespace

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --git a/HACKING b/HACKING
index 0ff1eef272439f7b29ed299b5dac841c176994f5..d8ee634b189e9561c54e76e11f8fa4736d8bcdc2 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -131,9 +131,12 @@
   merged even when they don't appear early in the list.
 
 * The 'master' and 'maint' branches should not be rewound, i.e., should
-  always fast-forward, except maybe for privacy issues.  For 'next' (if
-  that will ever be implemented), and for feature branches, the announcement
-  for the branch should document rewinding policy.
+  always fast-forward, except maybe for privacy issues.  For 'next'
+  (if that will ever be implemented), and for feature branches, the
+  announcement for the branch should document rewinding policy.  If a
+  topic branch is expected to be rewound, it is good practice to put
+  it in the 'experimental/*' namespace; for example, a rewindable branch
+  dealing with Vala support could be named like "experimental/vala-work".
 
 ============================================================================
 = Writing a good commit message