Rev 5955: Cleanup some obviously obsolete references in HACKING and code-review. in file:///home/vila/src/bzr/cleanup/reviews/

[Vincent Ladeuil]

At file:///home/vila/src/bzr/cleanup/reviews/

------------------------------------------------------------
revno: 5955
revision-id: v.ladeuil+lp at free.fr-20110606082445-c3ffk1shxl77vf7g
parent: pqm at pqm.ubuntu.com-20110602165709-ry228rc95pgnj3g9
committer: Vincent Ladeuil <v.ladeuil+lp at free.fr>
branch nick: reviews
timestamp: Mon 2011-06-06 10:24:45 +0200
message:
  Cleanup some obviously obsolete references in HACKING and code-review.
-------------- next part --------------
=== modified file 'doc/developers/HACKING.txt'
--- a/doc/developers/HACKING.txt	2010-11-12 22:43:38 +0000
+++ b/doc/developers/HACKING.txt	2011-06-06 08:24:45 +0000
@@ -117,12 +117,12 @@
 `your_lp_username`.  You can push your branch to Launchpad directly from
 Bazaar::
 
-  $ bzr push lp:~your_lp_username/bzr/meaningful_name_here
+  $ bzr push lp:~<your_lp_username>/bzr/meaningful_name_here
 
 After you have pushed your branch, you will need to propose it for merging to
 the Bazaar trunk.  Go to
-<https://launchpad.net/your_lp_username/bzr/meaningful_name_here> and choose
-"Propose for merging into another branch".  Select "~bzr/bzr/trunk" to hand
+<https://launchpad.net/~<your_lp_username>/bzr/meaningful_name_here> and choose
+"Propose for merging into another branch".  Select "lp:bzr" to hand
 your changes off to the Bazaar developers for review and merging.
 
 Alternatively, after pushing you can use the ``lp-propose`` command to 
@@ -254,10 +254,6 @@
     This file covers a brief introduction to Bazaar and lists some of its
     key features.
 
-NEWS
-    Summary of changes in each Bazaar release that can affect users or
-    plugin developers.
-
 setup.py
     Installs Bazaar system-wide or to your home directory.  To perform
     development work on Bazaar it is not required to run this file - you
@@ -285,6 +281,16 @@
     Documentation specifically targeted at Bazaar and plugin developers.
     (Including this document.)
 
+doc/en/release-notes/
+
+    Detailed changes in each Bazaar release (there is one file by series:
+    bzr-2.3.txt, bzr-2.4.txt, etc) that can affect users or plugin
+    developers.
+
+doc/en/whats-new/
+
+    High-level summaries of changes in each Bazaar release (there is one
+    file by series: whats-new-in-2.3.txt, whats-new-in-2.4.txt, etc).
 
 
 Automatically-generated API reference information is available at
@@ -576,7 +582,6 @@
 stuff covered above, "core" developers have responsibility for:
 
 * reviewing changes
-* reviewing blueprints
 * planning releases
 * managing releases (see `Releasing Bazaar <http://doc.bazaar.canonical.com/developers/releasing.html>`_)
 

=== modified file 'doc/developers/code-review.txt'
--- a/doc/developers/code-review.txt	2010-09-24 08:42:02 +0000
+++ b/doc/developers/code-review.txt	2011-06-06 08:24:45 +0000
@@ -66,7 +66,7 @@
   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 and/or in whats-new ?
+  appropriately documented in release notes and/or in whats-new ?
 
 * Does it meet the `coding standards <code-style.html>`_?