Owlcarousel2: Roadmap Announcement / Discussion

[daviddeutsch]

*_glances at the continuing stream of dozens of new issues filed each week_

So I just uploaded a roadmap that @pascalporedda and me worked out this week:

BIG stack of cards. The great news is that we managed to lobby for OwlCarousel quite heavily in our company and we'll have more time to spend on this in the future - you may have already noticed that we've started cutting down on the issue count with more coworkers chiming in (it was pushing close to 600 just weeks ago).

You can check out the roadmap here, but here are the thoughts behind our decisions. Note that every release will include a few bugfixes and feature additions and it's by no means a final plan - if pressing issues arise, we'll get to them.

2.3 - bugfixes, repo migration, minor features

(issues #1602, #1538, #1704, #1717)

First up, there is a bunch of housekeeping to do, get some urgent bugfixes and features in line and move the repo to our company org.

2.4 - finish up build pipeline, docs

(issues #1330, #1666, #1613)

Next, we need to finish the gulp pipeline transition and make sure all the docs are generated correctly under assemble.

2.5 - cloning & worker cleanup

(issues #1575, #1621, #1511)

There is one structural change we want to tackle in 2.x and that is cleaning up the clone generation and worker structure. That should mitigate a TON of bugs that pile up because things are quite off in that area.

2.6 - cleanup, code style, repo cleanup

(issues #1518, #1563, #1633, #1627, #1723, #1655)

Gearing up towards the 2.7 release, there will be one final cleanup around this release where we fix all the code style issues, old and/or outdated todos in the code and clean up all the old issues that we haven't gotten to yet.

2.7 - bugfixes & final, "LTS" release

(issues #1647, #1523, #1471, #1343)

We're confident that by this point, we'll have OwlCarousel at a level where it just works out of the box for 99% of its users without generating the same issues over and over again. That's why we want 2.7 to be a sort of Long Term Service release that will signify the last 2.x release. We'll continue to push bugfixes for it, but there won't be any further features.

3.0 - Typescript, additional plugins, breaking changes

As mentioned in a longer explanation in #1538, our long term goal is to rewrite OwlCarousel on TypeScript and redesign it to make it even more simple and foolproof. There are a few breaking changes we need for that, so we've pushed that off to our 3.0 plans.

As written above, additional issues will be scheduled into these releases as we work further through the stack, but that's our rough timeline.

Thanks everybody for being incredibly patient with us through this transition and please chime in with questions and/or suggestions!

[OwlCarousel2]

[franklinjavier]

:clap:

[odahcam]

Maybe opening a project could help you on the roadmap tasks tracking and center all the important stuff in one place. 😄

Most of issues here are a list of questions that should be in StackOverflow, even my issues appear on this list. 😕

[RicLeP]

Will you be making it vanilla JS rather and jQuery as there are lots of projects that could benefit from this.

[odahcam]

@RicLeP jQuery makes owlCarousel lighter, it's a very important and decisive carousel feature. Maybe Vue could do the same for Owl and kill jQuery dependency.

For VanillaJS you could use Swiper, you'll also note that Swiper's size is very very large compared to Owl.

[Basti93]

Will version 2.3.0 released this year? Do you have a concrete plan ?
Thank you for your work!

[yotewach]

I'm waiting for new update.

[dmcanaveral]

@daviddeutsch Do you have an ETA for the 2.3 release? I'm looking into/needing accessibility with keyboard control and I see that's next on your roadmap, but don't see dates or anything. Thanks for keeping owl going!

[pascalporedda]

@dmcanaveral Glad to tell you, that 2.3.1 has been released.

[odahcam]

Very nice, can we wait for some more features comming or should we stop dreaming?

[dmcanaveral]

@pascalporedda awesome, thanks for the good news!

[pascalporedda]

@odahcam There'll come new features

[gvillalonb]

how to slow down the carousel ?