Identify the issues that need to be resolved for the next stable release on D7.

Comments

DamienMcKenna created an issue. See original summary.

humansky’s picture

+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.

chris matthews’s picture

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?

solideogloria’s picture

Needs a new release, that's for sure.

izmeez’s picture

Looks like a good time to consider a tagged release with many issues that are RTBC and Drupal 9 release is fast approaching.

neslee canil pinto’s picture

Status: Active » Closed (outdated)
solideogloria’s picture

Status: Closed (outdated) » Active

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.

joelpittet’s picture

Status: Active » Fixed

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

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.