diff --git a/Netdisco/Changes b/Netdisco/Changes
index c0f84c55..82a8b410 100644
--- a/Netdisco/Changes
+++ b/Netdisco/Changes
@@ -1,3 +1,9 @@
+2.032002 - 2015-04-03
+
+  [ENHANCEMENTS]
+
+  * Update development pod to mention cpanm installdeps
+
 2.032001 - 2015-03-24
 
   [NEW FEATURES]
diff --git a/Netdisco/lib/App/Netdisco/Manual/Developing.pod b/Netdisco/lib/App/Netdisco/Manual/Developing.pod
index 7a057061..2ef40ab8 100644
--- a/Netdisco/lib/App/Netdisco/Manual/Developing.pod
+++ b/Netdisco/lib/App/Netdisco/Manual/Developing.pod
@@ -63,7 +63,12 @@ You can point at a different database without editing C<deployment.yml>:
 It's recommended to delete the "C<~/perl5/lib/perl5/App/Netdisco>"
 directory to avoid accidentally picking up old Netdisco code. For working on
 L<SNMP::Info> you can similarly delete "C<~/perl5/lib/perl5/SNMP/Info*>" and
-then symlink from "C<Info.pm>" and "C<Info>" to your git repo.
+then symlink from "C<Info.pm>" and "C<Info>" to your git repo. If you pull
+from upstream and the dependencies have changed, you can install them without
+re-installing Netdisco itself:
+
+ cd netdisco-ng/Netdisco
+ ~/bin/localenv cpanm --installdeps .
 
 Happy hacking!