Changes between Version 11 and Version 12 of SVN

Timestamp:

Feb 17, 2007, 10:26:35 PM (18 years ago)

Author:

Frederico Caldeira Knabben

Comment:

--

SVN

@@ -32 +32 @@
 Branches give us isolated environments for development, and once tested and confirmed a new work is ready, it can be simply merged in the trunk.
 
+For code that doesn't bring instability, like trivial fixes or small features, there is no need to work on a separated branch. It can be committed directly to the trunk if you feel the code is ok and it is well tested. It makes the management easier.
+
 The branches could be created in the following spaces:
 
@@ -52 +54 @@
 [TODO]
 
+== Committing ==
+
+Try to make a single commit for each fix or feature. Avoid making big commits with lots of changes. This separation makes each commit an isolate thing. It makes code review and merge tasks easy.
+
+The commit log message is very important. Don't underestimate it. It must be well written and informative. Whenever possible, make references to related trac items, like tickets or changesets. You may use one of the "standard" messages, like the following examples:
+
+ * Fixed #81: IE has a DOM bug that caused FCKDomTools.RTrimNode to break. 
+ * Merged trunk r131:132 into branches/versions/2.4.x
+ * FCKeditor 2.4 tagging
+
 == Links ==