Changes between Version 19 and Version 20 of HowToBackport

Timestamp:

04/14/13 04:07:59 (12 years ago)

Author:

hamish

Comment:

--

HowToBackport

@@ -12 +12 @@
 A: It depends: preferably a developer should be able to backport him/herself but
  * do not break the release branch :o)
-   * ''(i.e. don't leave it in a broken state for days while you are working on something, we must be ready for an emergency release at any time)''
+   * ''i.e. don't leave it in a broken state for days while you are working on something, we must be ready for an emergency release at any time.''
  * make your commits to the dev branch first
+   * ''do testing and bug fixes in a safe place, then backport in an "atomic commit" to the release branch. Others may do the backport, and they'll assume that the dev branch is the most recent version to use.''
  * make tests
  * only fix bugs, do not introduce new features
  * Only do refactoring in trunk
-   * ''(large and complicated changes can introduce new hard to spot bugs, the idea of the stable branch is to asymptote to zero bugs)''
+   * ''large and complicated changes can introduce new hard to spot bugs, the idea of the stable branch is to asymptote to zero bugs.''
 
 If the above is unclear, it should be discussed on the developers list. '''If in doubt, ask! '''