Rev 5433: Tweak code-review and code-style a bit (NOT controversial :) in file:///home/vila/src/bzr/releases/work/

[Vincent Ladeuil]

At file:///home/vila/src/bzr/releases/work/

------------------------------------------------------------
revno: 5433
revision-id: v.ladeuil+lp at free.fr-20100924084202-q9krob6st75oegjx
parent: v.ladeuil+lp at free.fr-20100924084033-0ehn0nrovthrhuvo
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: work
timestamp: Fri 2010-09-24 10:42:02 +0200
message:
  Tweak code-review and code-style a bit (NOT controversial :)
-------------- next part --------------
=== modified file 'doc/developers/code-review.txt'
--- a/doc/developers/code-review.txt	2010-05-14 13:34:22 +0000
+++ b/doc/developers/code-review.txt	2010-09-24 08:42:02 +0000
@@ -9,7 +9,7 @@
 
 Normally changes by core contributors are reviewed by one other core
 developer, and changes from other people are reviewed by two core
-developers.  Use intelligent discretion about whether if the patch is trivial.
+developers.  Use intelligent discretion about whether the patch is trivial.
 
 No one likes their merge requests sitting in a queue going nowhere: this 
 is pure waste.  We prioritize reviewing existing proposals.  
@@ -66,9 +66,9 @@
   blackbox (command-line level) and API-oriented tests?
 
 * If this change will be visible to end users or API users, is it
-  appropriately documented in NEWS?
+  appropriately documented in NEWS and/or in whats-new ?
 
-* Does it meet the coding standards below?
+* Does it meet the `coding standards <code-style.html>`_?
 
 * If it changes the user-visible behaviour, does it update the help
   strings and user documentation?

=== modified file 'doc/developers/code-style.txt'
--- a/doc/developers/code-style.txt	2010-09-13 08:20:57 +0000
+++ b/doc/developers/code-style.txt	2010-09-24 08:42:02 +0000
@@ -78,9 +78,9 @@
 ===============
 
 Bazaar supports Python from 2.4 through 2.6, and in the future we want to
-support Python 3.0.  Avoid using language features added in 2.5 or 2.6, or
-features deprecated in Python 3.0.  (You can check v3 compatibility using
-the ``-3`` option of Python2.6.)
+support Python 2.7 and 3.0.  Avoid using language features added in 2.5,
+2.6 or 2.7, or features deprecated in Python 3.0.  (You can check v3
+compatibility using the ``-3`` option of Python2.6.)
 
 Specifically: