Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Calendar 7.x-3.5 was released in October 2014 (over 4 years ago). Since then most of the development time has understandably been focused on the 8.x-1.x branch, which is very much appreciated! Would it be possible to tag a 7.x-3.6 release that at least includes Commit 6164043 on 7.x-3.x that fixes Issue #2160183: Undefined index: groupby_times as well as the 7.x issues with RTBC status?
Additionally, which of the current 7.x issues that needs work and needs review should also be included in the 7.x-3.6 release?
There still hasn't been a 7.x-3.6 release, so this shouldn't be closed as Outdated -- leave it open until it can be marked Fixed.
Either mark the Drupal 7 branch as needing a new maintainer or tag a release, please. Considering that 90% of the module's users are still using the 7.x branch, I don't understand why we have to wait so many years for a release when the child issues are all RTBC or committed.
Sorry for the wait, I'm a new co-maintainer, but strapped for time as we all are, squeezed this in tonight, with a bit of luck there won't be too much blowback 🤞🚀
I committed the last two RTBC'd issues mapped to this and opened a new one for 3.7
Comments
Comment #2
humansky commented+1 for this issue
It's been a while since 3.5 was released. I'm always hesitant to switch to a dev release, but I might have to if a 3.6 version isn't released soon.
Comment #3
chris matthews commentedCalendar 7.x-3.5 was released in October 2014 (over 4 years ago). Since then most of the development time has understandably been focused on the 8.x-1.x branch, which is very much appreciated! Would it be possible to tag a 7.x-3.6 release that at least includes Commit 6164043 on 7.x-3.x that fixes Issue #2160183: Undefined index: groupby_times as well as the 7.x issues with RTBC status?
Additionally, which of the current 7.x issues that needs work and needs review should also be included in the 7.x-3.6 release?
Comment #4
solideogloria commentedNeeds a new release, that's for sure.
Comment #5
izmeez commentedLooks like a good time to consider a tagged release with many issues that are RTBC and Drupal 9 release is fast approaching.
Comment #6
neslee canil pintoComment #7
solideogloria commentedThere still hasn't been a 7.x-3.6 release, so this shouldn't be closed as Outdated -- leave it open until it can be marked Fixed.
Either mark the Drupal 7 branch as needing a new maintainer or tag a release, please. Considering that 90% of the module's users are still using the 7.x branch, I don't understand why we have to wait so many years for a release when the child issues are all RTBC or committed.
Comment #8
joelpittetSorry for the wait, I'm a new co-maintainer, but strapped for time as we all are, squeezed this in tonight, with a bit of luck there won't be too much blowback 🤞🚀
I committed the last two RTBC'd issues mapped to this and opened a new one for 3.7