Stop your VCS hook to update version!
authorOleksandr Gavenko <gavenkoa@gmail.com>
Fri, 21 Oct 2011 00:47:10 +0300
changeset 1042 dd197cbdaf21
parent 1041 643877f0e84f
child 1043 3785e14cca53
child 1049 a1e7d8884936
Stop your VCS hook to update version!
devel-versioning.rst
--- a/devel-versioning.rst	Thu Oct 20 02:04:04 2011 +0300
+++ b/devel-versioning.rst	Fri Oct 21 00:47:10 2011 +0300
@@ -124,6 +124,23 @@
  * QA test results (Pass/Fail).
  * Location of full logs.
 
+Stop your VCS hook to update version!
+=====================================
+
+Don't update version without human decision.
+
+Why do not do this on success build:
+
+ * You can have several build machine which may concurrently update version.
+ * There not exist tools for easy querying for status of build (as ok/fail,
+   build configuration, date, coverage, lint checks, etc).
+ * Some part of development team may not have permission for bumping version and
+   after build they must revert some automatically updated files.
+
+Why do not do this from pre-/post-commit hooks:
+
+ * Some changes can only partially introduce feature/bugfix.
+
 Version ordering formula.
 =========================