Closed (won't fix)
Project:
ImageCache Actions
Version:
7.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
25 Oct 2011 at 11:44 UTC
Updated:
1 Dec 2012 at 19:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
fietserwinNice idea. We don't have that overview ourselves, while it would be very handy to create/prioritize/assign tasks for ourselves, but indeed also for users.
When I start working on this list, I will only do so for the 7.x version(s), but will add if support is known to be buggy (besides a simple yes/no).
Comment #2
khaled.zaidan commentedGreat!
Even if not much detail is included in the table, it will still be a start, and others (including me) can later add on to it with time.
Comment #3
dman commentedIMO, not the sort of thing that can/should be managed manually online. Either it's up-to-date or its not.
There are also a number of wacky library dependencies (GD version, PHP build, Imagemagick version, font rendering lib) that also affect what works where.
This is why I added the imagecache_actions testsuite add-on module to get a realtime sanity check on the number of things that can go wrong. However, that in itself introduced a number of dependencies (eg features module) just to bootstrap itself. :-/
It's an issue I'm aware of, but until we set up a network of machines on different OS-s to contribute to a central test result server (yeah right) there is an amount of uncertainty over what will work perfectly everywhere all the time.
Suggestions are open however.
Attached is a snapshot of what happens when (dev) tests fail half the time (not uncommon). and some of the more visible differences between the toolkits.

I really hope to improve the management of this testsuite to the point where its own internal failings stop outweighing the errors it shows up.
Comment #4
fietserwinThis is part of the roadmap, so doesn't needs its own issue.