diff --git a/release/NOTES.txt b/release/NOTES.txt
new file mode 100644
index 00000000..cde4c02a
--- /dev/null
+++ b/release/NOTES.txt
@@ -0,0 +1,18 @@
+o There are N snapshot dependencies, would you like to update them
+  to use timestamped version?
+  
+o Foreach snapshot dependency:
+    -> display current dependency information
+    -> show what the updated information would be
+    -> prompt user to allow update
+    
+o Would you like the update POM to be written out for the release?
+
+---
+
+o Add whatever hooks that would allow this in a UI environment. The
+  POM transformer can be used for anything really. When Jaxen beans
+  walks we can align inheritance. Console/GUI.
+o backing up the old POM
+o do we allow it to be flipped back to snapshots?
+    
diff --git a/release/src/main/org/apache/maven/release/SnapshotResolver.java b/release/src/main/org/apache/maven/release/SnapshotResolver.java
index b334cdb4..9acabd6d 100644
--- a/release/src/main/org/apache/maven/release/SnapshotResolver.java
+++ b/release/src/main/org/apache/maven/release/SnapshotResolver.java
@@ -64,12 +64,11 @@ import org.dom4j.Node;
 import java.io.File;
 
 /**
- * This is a simple POM manipulator that doesn't take into account any sort of
- * POM inheritance. When the interpolation and inheritance is cleaned up in the
- * Maven we will be able to serialize a POM directly with greater ease. But we
- * may stick with this Jaxen solution anyway because it's so easy. Just turn the
- * POM in memory into a Dom4j document and perform the same operation as we are
- * here.
+ *
+ *
+ * @author <a href="mailto:jason@zenplex.com">Jason van Zyl</a>
+ *
+ * @version $Id: SnapshotResolver.java,v 1.3 2003/02/10 15:57:06 jvanzyl Exp $
  */
 public class SnapshotResolver
     extends AbstractPomTransformer