summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAdrian Sampson <adrian@radbox.org>2014-02-26 20:31:06 -0800
committerAdrian Sampson <adrian@radbox.org>2014-02-26 20:31:06 -0800
commitf9a820d303c8240461b19a502e4b58fc7c61ab95 (patch)
tree0ecbcbbdb425f26148c9ab84b358717386bf9975
parent472571a4c699741c2fa9560101ca1605e1e80a86 (diff)
summarize changelog for 1.3.3 releasev1.3.3
-rw-r--r--docs/changelog.rst14
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/changelog.rst b/docs/changelog.rst
index 53fbce4eb..994053861 100644
--- a/docs/changelog.rst
+++ b/docs/changelog.rst
@@ -1,11 +1,13 @@
Changelog
=========
-1.3.3 (in development)
-----------------------
+1.3.3 (February 26, 2014)
+-------------------------
-Version 1.3.3 brings a set of internal changes to how fields work. The
-consequences for all users are:
+Version 1.3.3 brings a bunch changes to how item and album fields work
+internally. Along with laying the groundwork for some great things in the
+future, this brings a number of improvements to how you interact with beets.
+Here's what's new with fields in particular:
* Plugin-provided fields can now be used in queries. For example, if you use
the :doc:`/plugins/inline` to define a field called ``era``, you can now
@@ -24,7 +26,9 @@ consequences for all users are:
changes.
For developers, the short version of the story is that Item and Album objects
-provide *uniform access* across fixed, flexible, and computed attributes.
+provide *uniform access* across fixed, flexible, and computed attributes. You
+can write ``item.foo`` to access the ``foo`` field without worrying about
+where the data comes from.
Unrelated new stuff: