Problem/Motivation
Drupal 11 may be released already in June 2024.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork leaflet-3425163
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
ressaComment #4
ressaComment #5
orkutmuratyilmazI've tested it locally. @ressa, thanks for the D11 compatibility:)
Comment #6
itamair commentedok ... thanks @here!
I am going to sit for final green flag for merging this Geofield Drupal 11 compatibility Issue:
https://www.drupal.org/project/geofield/issues/3430742
and then will proceed with this one also ... :-)
Comment #8
itamair commentedThanks. This was merged and is going to be part of the next Leaflet 10.2.18 incoming release.
Comment #9
ressaThanks @itamair, and @Orkut Murat Yılmaz for reviewing!
To prevent abuse, for example by creating a branch or uploading a file only to get credit (I searched, but can't find the issue where it was decided), credits are no longer added automatically. So the maintainer needs to remember do it ...
Comment #10
ressaI found the issue, where I asked about the history about disabling automatic crediting, and @fjgarlin kindly cleared it up:
In the Gitlab issue system, where Drupal issues are moving soon, crediting will be part of the process of closing an issue, from #3395901-28: Use Gitlab CI in Simplenews:
Comment #12
ressaWhat is strange is that it says (#7) "Issue #3425163 by ressa, Orkut Murat Yılmaz: Support Drupal 11 in..." but under "Credit & committing", it says this:
Though it's not listed under my credited issues for Leaflet:
From Leaflet issues credited to ressa.
Comment #13
ressaI just checked, and found two issue where I could have gotten credit as well ...