Start to do a little release tracking

RELEASE_NOTES.txt

@@ -0,0 +1,29 @@
+Release 0.2.0:
+===============
+Focus on API cleanup and better configurability.
+
+* Reworked the query API
+  * QueryOpts usage was a bit clumsy, so it is no longer exposed as a 
+    parameter in the query API.  Instead, it's used internally to consolidate 
+	settings, but the query instance functions more as a builder:
+
+	Query with start and end keys:
+		Query q = service.query();
+		q.start( startkey )
+		 .where( Criteria.eq( 'prop', value ) )
+		 .where( Criteria.eq( 'prop2', value2 ) )
+		 .end( endkey );
+		q.execute();
+
+    or for an indexed query:
+        Query q = service.query();
+		q.using( Criteria.eq( 'idxprop', value ) )
+         .where( Criteria.gt( 'prop2', minvalue ) );
+		q.execute();
+
+
+
+
+Release 0.1.0:
+===============
+Initial code release.

TODO.txt

@@ -12,29 +12,5 @@
 
 10/8/2009: 
 
-* Straight scans aren't very intuitive with the query API, you kind of
-  work-around it to get them.  Need to more easily enable this common
-  usage. 
-
 * For query scanning of secondary index tables, should maybe use row
   prefix filters instead of value filters
-
-1-28-2010:
-
-* Rework the query API
-  * QueryOpts is clumsy.  It shouldn't be exposed as an external
-    object.  Instead, use it internally to consolidate settings, but
-	the query instance should function more as a builder:
-		q = service.query();
-		q.start( startkey )
-		 .where( Criteria.eq( 'prop', value ) )
-		 .where( Criteria.eq( 'prop2', value2 ) )
-		 .end( endkey );
-		q.execute();
-
-    or for an indexed query:
-        q = service.query();
-		q.using( Criteria.eq( 'idxprop', value ) )
-         .where( Criteria.gt( 'prop2', minvalue ) );
-		q.execute();
-