Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After two beta releases and a release candidate, identify the issues that need to be resolved in order to do the final 7.x-2.9 release.
Comments
Comment #1
vijaycs85not sure if we have any more issue to get in. However there were few regression on beta releases. We may need to spend sometime testing the HEAD -> tag -> release.
Comment #2
MustangGB CreditAttribution: MustangGB commented#1190830: Disabled Date value not properly handled has passed manual testing, I'll be honest I don't really understand the automated testing stuff stickywes is doing, but perhaps a maintainer could help push this though before 2.9?
Comment #3
DamienMcKenna@vijaycs85: Yeah, #998076: Problem with timezone handling (caused by date_get_timezone_db returning only UTC) caused problems for lots of sites, hopefully we can get it to RTBC and ready for committing.
Comment #4
Shai CreditAttribution: Shai commentedCalendar Block Next/Prev Navigation is Broken remains without a fix and is important.
Comment #5
DamienMcKennav7.x-2.9 was released: https://www.drupal.org/node/2565073
Several items listed here weren't resolved, and the release introduced some regressions, so lets bump this to the next release.
Comment #6
rcodina CreditAttribution: rcodina commentedI think a 7.x-2.10 release should be done soon because I have to use the dev version of Date so next/prev buttons on Calendar module works well:
#2375235: Calendar block Next/Prev navigation broken
Comment #7
vijaycs85Looks like RC1 was around a year back and we got 2 commit since then. Is it time for 2.10 stable? @DamienMcKenna are you OK for me to release make 2.10 release?
Comment #8
DamienMcKenna@vijaycs85: Why are you asking me? :-) That said, I really think the RTBC patches referenced on this issue should be committed (several of them are affecting our ability to fix things), and the other two should imho be finished off.
Comment #9
vijaycs85@DamienMcKenna: Sorry, if it came as obligated direct request. As I spent very little time on date issues and since you have raised this request, thought you might have list of things want to be in 2.10.
Comment #10
vijaycs85Committed below issues:
- #2780415: As per Drupal coding standards, use uppercase for PHP constants
- #2646646: Tests are broken on current 7.x-2.x branch
- #2412049: DateMigrateExampleUnitTest fails if migrate is missing
- #2186191: missing help text
Comment #11
DamienMcKennaSorry for the confusion, I create plan issues like this to help maintainers and contributors, but I don't want to seem like I'm dictating what to work on.
BTW I looked at a few issues and pulled some that weren't passing tests, and found some others that are passing tests and have already been RTBC'd. There also seems to be a general problem with PHP 7, so I opened a new issue to look into that.
Comment #12
vijaycs85Thank you so much for all the efforts @DamienMcKenna. much appreciated.
No problem and thanks for doing it. This plan issue is really very helpful.
I committed few few before merging the test fix @steve worked on. Hopefully the ones I pushed don't break or introduce new test fails. Looks like PHP 5.3 is green on 7.x-2.x. I just queued few others (5.4, 5.5 and 5.6) as the last run was last year this time.
Cool, thanks.
Comment #13
vijaycs85Released 7.x-2.10 at https://www.drupal.org/project/date/releases/7.x-2.10-rc2 Thank you everyone!
Comment #14
DamienMcKennaThanks. I'll bump the other issues to 2.11.