add some extra error reporting to I/O layer tests

[imager.git] / Changes

diff --git a/Changes b/Changes
index 73bc8c45b00dd2e73c3159a86ed27c4993fd01d0..ed008d19455d4ab4bf2c11180810b425c2e289bd 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,13 +1,24 @@
 Imager release history.  Older releases can be found in Changes.old
 
+Imager 1.004_002 - 20 Mar 2016
+================
+
+ - don't use the seek() method on opened() handles in
+   t/200-file/400-basic.t.  In older versions of perl such handles are
+   only IO::Handle objects, not IO::File, and don't have a seek()
+   method.
+
+Imager 1.004_001 - 16 Mar 2016 (Birthday release - but not my birthday)
+================
+
  - re-work the t/200-file/400-basic.t to correctly handle failures
    It's custom ok() function didn't have a prototype and didn't use scalar().
    This caused ok() to use the note instead of the value being tested when
    the method called returned an empty list.  For an example of the problem
    caused see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812093
 
- - remove some noise from when Imager tried to work with buggy
-   versions of giflib.
+ - remove some noise from when Imager tried to work with bugs in old
+   versions of giflib.  I can't do much about the new bugs.
 
  - the new autolevels filter (Imager 0.99) used an integer for the
    sample scaling factor which caused the top output level to be too
@@ -42,6 +53,18 @@ Imager release history.  Older releases can be found in Changes.old
    - the nearest_color filter (undocumented until I find a use for it)
      leaked both temporaries passed to the API and internal buffers
 
+   - the internal process of upgrading a paletted image to a direct
+     color image would leak a context object reference count.
+
+   - a write failure when writing to a GIF file could leak memory.
+
+   - failing to write to a 1-bit/pixel ICO image could leak memory.
+
+ - Imager no longer deliberately leaks the context object from the
+   initial thread.  This was done to ensure there was always a context
+   object available, but the code that needed that now handles the
+   lack correctly,
+
  - fixed some uninitialized memory usage detected by valgrind:
 
    - rotate()/i_rotate_exact()/i_rotate_exact_bg()/i_matrix_transform()/