we are currently working on replacing Galleria, the base JS library used on the carousel tile, with Cycle2.
djowett has put a lot of effort on this trying to maintain compatibility but I'm not pretty sure about it; I want to kill Galleria on the next release because the code is becoming to complex and I don't want to have to maintain in.
what does this mean for you? if you are using collective.cover and have customized the carousel tile in some way, you will have to work on it again before you upgrade.
if you have no customizations, we will give you a smooth upgrade requiring you only to manually uninstall collective.js.galleria.
please come to GitHub and participate on the discussion: should we just get rid of Galleria or should we maintain compatibility at least for one release? what's the best way to accomplish it?
Personally, providing they're mindfully implemented ( http://bradfrostweb.com/blog/post/carousels/ ), I have nothing against carousels. For photo galleries, where it's not crucial the user views images, it's a quick and easy interaction that makes a lot of sense.
As I understand it, Foundation deprecated their Carousel not because of usability, but because there were a lot of other easily integrated good offerings out there & I guess they found it a big overhead to keep up. Having worked with Orbit & Cycle2 I prefer the later.