CHANGELOG in timeframe-0.2.0 vs CHANGELOG in timeframe-0.2.1

@@ -1,4 +1,10 @@
+0.2.1 / 2012-04-24
+
+* Bug fixes
+
+  * Stop defining Timeframe#to_json... it's conventional to only define #as_json
+
 0.2.0 / 2012-04-24
 
 * Breaking changes
 
   * Use ISO8601 for JSON output. No sense in coming up with our own structure. Timeframe.parse will still understand the old startDate/endDate hash structure.