Reorganize v0.8 changelog

docs/changes.rst

@@ -7,24 +7,7 @@ This change log is used to track all major changes to Mopidy.
 v0.8 (in development)
 =====================
 
-**Changes**
+**Audio output and mixer changes**
-
-- Added tools/debug-proxy.py to tee client requests to two backends and diff
-  responses. Intended as a developer tool for checking for MPD protocol changes
-  and various client support. Requires gevent, which currently is not a
-  dependency of Mopidy.
-
-- Fixed bug when the MPD command `playlistinfo` is used with a track position.
-  Track position and CPID was intermixed, so it would cause a crash if a CPID
-  matching the track position didn't exist. (Fixes: :issue:`162`)
-
-- Added :option:`--list-deps` option to the `mopidy` command that lists
-  required and optional dependencies, their current versions, and some other
-  information useful for debugging. (Fixes: :issue:`74`)
-
-- When unknown settings are encountered, we now check if it's similar to a
-  known setting, and suggests to the user what we think the setting should have
-  been.
 
 - Removed multiple outputs support. Having this feature currently seems to be
   more trouble than what it is worth. The :attr:`mopidy.settings.OUTPUTS`
@@ -36,9 +19,9 @@ v0.8 (in development)
 
 - Switch to pure GStreamer based mixing. This implies that users setup a
   GStreamer bin with a mixer in it in :attr:`mopidy.setting.MIXER`. The default
-  value is ``autoaudiomixer``, a custom mixer that attempts to find a mixer that
+  value is ``autoaudiomixer``, a custom mixer that attempts to find a mixer
-  will work on your system. If this picks the wrong mixer you can of course
+  that will work on your system. If this picks the wrong mixer you can of
-  override it. Setting the mixer to :class:`None` is also supported. MPD
+  course override it. Setting the mixer to :class:`None` is also supported. MPD
   protocol support for volume has also been updated to return -1 when we have
   no mixer set.
 
@@ -46,7 +29,7 @@ v0.8 (in development)
 
 - Updated the NAD hardware mixer to work in the new GStreamer based mixing
   regime. Settings are now passed as GStreamer element properties. In practice
-  that means that the following old-style config:
+  that means that the following old-style config::
 
       MIXER = u'mopidy.mixers.nad.NadMixer'
       MIXER_EXT_PORT = u'/dev/ttyUSB0'
@@ -54,7 +37,7 @@ v0.8 (in development)
       MIXER_EXT_SPEAKERS_A = u'On'
       MIXER_EXT_SPEAKERS_B = u'Off'
 
-  Now is reduced to simply:
+  Now is reduced to simply::
 
       MIXER = u'nadmixer port=/dev/ttyUSB0 source=aux speakers-a=on speakers-b=off'
 
@@ -62,20 +45,41 @@ v0.8 (in development)
   properties may be left out if you don't want the mixer to adjust the settings
   on your NAD amplifier when Mopidy is started.
 
-- Fixed :issue:`150` which caused some clients to block Mopidy completely. Bug
+**Changes**
-  was caused by some clients sending ``close`` and then shutting down the
-  connection right away. This trigged a situation in which the connection
-  cleanup code would wait for an response that would never come inside the
-  event loop, blocking everything else.
 
-- Created a Spotify track proxy that will switch to using loaded data as soon
+- When unknown settings are encountered, we now check if it's similar to a
-  as it becomes available. Fixes :issue:`72`.
+  known setting, and suggests to the user what we think the setting should have
+  been.
 
-- Fixed crash on lookup of unknown path when using local backend.
+- Added :option:`--list-deps` option to the ``mopidy`` command that lists
+  required and optional dependencies, their current versions, and some other
+  information useful for debugging. (Fixes: :issue:`74`)
+
+- Added ``tools/debug-proxy.py`` to tee client requests to two backends and
+  diff responses. Intended as a developer tool for checking for MPD protocol
+  changes and various client support. Requires gevent, which currently is not a
+  dependency of Mopidy.
 
 - Support tracks with only release year, and not a full release date, like e.g.
   Spotify tracks.
 
+**Bug fixes**
+
+- :issue:`72`: Created a Spotify track proxy that will switch to using loaded
+  data as soon as it becomes available.
+
+- :issue:`162`: Fixed bug when the MPD command ``playlistinfo`` is used with a
+  track position. Track position and CPID was intermixed, so it would cause a
+  crash if a CPID matching the track position didn't exist.
+
+- :issue:`150`: Fix bug which caused some clients to block Mopidy completely.
+  The bug was caused by some clients sending ``close`` and then shutting down
+  the connection right away. This trigged a situation in which the connection
+  cleanup code would wait for an response that would never come inside the
+  event loop, blocking everything else.
+
+- Fixed crash on lookup of unknown path when using local backend.
+
 
 v0.7.3 (2012-08-11)
 ===================