IS this module abandoned?

@ajayg This module is stable. But, it doesn't just work out of the box. You need to theme it to fit your content and design. In order to avoid all the support requests I have not published a release.

In order to get a release someone needs to support all the theming related support requests that will come in.

@mfer: I understand your desire to avoid all the support requests, but by not publishing a stable release, you effectively opt-out of the Drupal security team’s efforts, so this module will not receive any security audits, nor will found vulnerabilities be handled by the security team.

If you don’t want to deal with support requests for theming this, you could just say so on the project page and on the issue submission page. Refraining from marking code as stable just to avoid support requests is a dangerous precedent.

There are projects that would like to work with Views Carousel but are now considering removing their support because there's no public release of the module. See: http://groups.drupal.org/node/78303#comment-247899

If you just need warm themer-type bodies to help with support requests, please do publish the module I can help out with that and will try to find other themers to keep an eye on the queue.

I agree with mikl (and ajayg and emmajane).

I'm using this module on productions sites but I would rather not use -dev versions since they are moving targets and many of my clients prefer not to have any -dev versions of modules (unfortunately there's this sort of "fear" of releasing stable versions, I know a lot of good modules that would benefit a lot from a stable release but for various reasons the maintainers won't).

There is no need to support all theme issues just because you release a stable version. As the others have said already, explain it on the project page. And let us who appreciate the module help out if we're able to.

ok ok. Expect a release in the next week. I need to look this module over first.

Just for an update, I got swamped with client work so this got held off a little. But, I have a place to use it in the coming months so I will get this released!

For everyone wondering the status of this module. With a little prodding from drewish I moved the 1.x branch to RC and hope to have a final release soon. I'm unsure of what will become the status of the 2.x branch because of 3 reasons....

1) I'm aware of several bugs that need to be fixed in that branch. The 1.x branch has basically the same features but doesn't rely on the jcarousel module. The bugs I know of in the 2.x branch are not in the 1.x branch.

2) I'm not all that familiar with the 2.x branches code. It was written by Rob Loach to use jcarousel as a dependency. I'm not really familiar with the code in that module either. And....

3) I just became the owner of the carousel namespace on d.o. The goal there will be to have a base carousel module with other modules that take advantage of it. One for views (what would have been views_carousel 3.x, one for cck, etc.). This is where my mind it as for the moment.

If someone wants to work on the 2.x branch to move it towards a release I'm all for that. It would be great. Please contact me if you do.

There has been a release of the 1.x branch. I know it's not the release of the 2.x branch many had wanted but, there were some technical and time limitations to doing that.

The module is clearly not abandoned, so I can see why this issue is "fixed", but what does this mean for a stable release of the 2.x branch?

@AdrianB I do not have time to work on the 2.x branch. I chose to make the 1.x branch a release because it has far less bugs, it is what I originally wrote, and I was asked to release a stable of that branch.

If someone wants to start rolling patches they are more than welcome. I know of a number of bugs.

If you are not using jcarousel module for anything else or do not need to have jcarousel on the page in more ways than viewscarousel I would take a look at moving to the 1.x branch. It is much more stable.

Thanks for the answer. Maybe I'll switch to the 1.x branch.

(I wish I could help with patches, but I just don't have that knowledge (yet).)