ROADMAP.txt 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. Imagecache Actions roadmap
  2. --------------------------
  3. This is a non-contractual roadmap for the D7 branch of the imagecache actions
  4. module. Actual release dates and completed features will largely depend on
  5. available time. So support is always welcome. Furthermore, critical bugs may
  6. make us release more often, but that should only change the release number in
  7. which certain features are planned, not the timeline.
  8. Imagecache Actions 7.x-1.0
  9. --------------------------
  10. Targeted release date: may 2012
  11. - (DONE) Clean up D7 issue queue
  12. - (DONE) Commit posted patches from the issue queue
  13. - (DONE) Solve easy to solve bug reports
  14. - Do some basic testing
  15. - (DONE) Reintroduce the text action, currently living in a sandbox project at
  16. http://drupal.org/node/1090312
  17. - (DONE) Update README.txt
  18. - (DONE) Introduce CHANGELOG.txt
  19. - (DONE) Add this ROADMAP.txt
  20. Imagecache Actions 7.x-1.1
  21. --------------------------
  22. Targeted release date: end 2012
  23. Mainly a bug fix release
  24. - (DONE) Solve remaining outstanding bug reports
  25. - (ALMOST DONE) Keep D7 issue queue clean
  26. Imagecache Actions 7.x-1.2
  27. --------------------------
  28. Targeted release date: spring 2013
  29. - Check help and documentation. a.o: hook_help, effect descriptions.
  30. - Continue to keep the D7 issue queue clean.
  31. - Improve Imagemagick support and/or document what effects are not working for
  32. which toolkit (version).
  33. - Check that all effects implement all of the effects API (especially the
  34. dimensions callback).
  35. - Add testing. The idea is to create a set of image styles that cover all
  36. effects and can be used to visually check for regressions.
  37. Automated testing would be nice, but I am not sure that we can guarantee that
  38. jpeg or png files are binary identical on each run across different computers.
  39. But if the number of false positives is small, it would certainly be a useful
  40. addition.
  41. Imagecache Actions 7.x-1.3
  42. --------------------------
  43. Targeted release date: ...
  44. - Look at outstanding feature requests
  45. - Continue to keep the D7 issue queue clean
  46. - Keep improving Imagemagick support, a.o:
  47. - Try to get insight into what version of imagemagick is required by what
  48. effect.
  49. - Document which effects might produce different results.
  50. - Refactor code
  51. - Extract common form fields
  52. - Extract common error handling
  53. - (STARTED) Clean up comments, todo's, etc.
  54. - (STARTED) Doxygen code documentation according to latest standards
  55. - Increase the amount of lazy loaded code
  56. Imagecache Actions 7.x-2.x
  57. --------------------------
  58. Targeted release date: ...
  59. - Can we refactor effects into auto loading class based plugins? What does
  60. CTools offer in these? How do D8 core effects do this?
  61. - If so, will it make implementing new effects much simpler? Because that is
  62. what we should strive for.
  63. - Should we rename the module to image_effects?
  64. - If we manage to provide an easy to use plugin system, we should strive to
  65. merge with other modules that provide effects:
  66. - FiltersIE module (http://drupal.org/project/filtersie)
  67. - Imagecache Effects: http://drupal.org/project/imagecache_effects (D6 only,
  68. but are their effects more advanced then our counterparts or do they add new
  69. effects?)
  70. - Image watermark: http://drupal.org/project/watermark (D5 only, but is their
  71. watermark effect more advanced?)
  72. - ImageCache Scale-9 Actions: http://drupal.org/project/imagecache_scale9actions
  73. - etc.