Jump to:
| Project: | Views carousel |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
The new jCarousel 2.0 module now includes all the functionality of the Views Carousel project. Considering the 2.x version of Views Carousel actually depends on jCarousel (1.x), it seems like a good course of action is to simply deprecate Views Carousel entirely and refer users over to jCarousel. I'm sure many people will find needing one less dependency a welcome change.
Regarding the "Carousel" project, which had been planned to be the merging of jCarousel and Views Carousel, discussions with Matt Farina (and then indirectly with Rob Loach), we agreed to put our work into the 2.x branch of jCarousel instead of starting yet-another-carousel-project. The new jCarousel 2.x branch has already begun porting to Drupal 7 also, one more area where we can pool our resources instead of having 4+ separate carousel projects.
Comments
#1
I closed #929810: merge with similar modules as a duplicate, since this post is a bit more direct in the request.
By "deprecate" I mean that we should do the following:
- Refer users over to jCarousel 2.0 on the project page.
- Set the "Recommended version" to "None", making the project downloads yellow instead of green on the project page (this makes it so that the module doesn't scream at you in Update Status but it should discourage new downloads).
- Mark the project development status as "Obsolete"
- After a transition period of time, close the issue queue, change the project maintenance status to "Abandoned", and mark the project downloads unsupported.
#2
I updated the project page to refer to jcarousel and the 2.x branch. The recommended version of the Drupal 6 branch is none. Because this module provides Drupal 5 support I'm leaving the project open for the time being.