Version 5.0.0 Released

[Alexandre-T]

Version 5.0.0 Released

Compatibility and Support

• Version 5.0.0 is now compatible with the stable version of doctrine/orm:3.1 while maintaining compatibility with the previous stable version, 2.9.
• Currently, this version is also compatible with the incoming versions of doctrine/orm, the "3.2.x-dev" and "4.0.x-dev" versions. These versions are not released yet.
• Version 5.0.0 remains functional with MySQL 5.7. However, please note that MySQL 5.7 is already obsolete. No security or maintenance updates will be provided for any features related to MySQL 5.7.
• Version 5.0.0 is no longer based on the CrEOF/*-parser . I forked these three packages and maintain them. ( longitude-one/wkt-parser , longitude-one/wkb-parser, longitude-one/geo-parser)
• Version 4 of longitude-one/doctrine-spatial is obsolete and no longer maintained.

Branch Maintenance

The main branch remains synchronous with 5.0.* versions.

Additional Notes

For more detailed information on the changes included in version 5.0.0, please refer to the release notes.
As always, I encourage you to update to the latest version of the package to benefit from the latest features and security improvements.

Upcoming Version 6.0.x

Branch Roadmap

• The 6.0.x branch will contain deployments for the upcoming version 6.

Breaking Changes

• Version 6 will no longer be compatible with PHP 8.1.
• It will introduce a complete overhaul of PHP type constructors. These constructors will accept a specific number of arguments:
  • x, y, and srid for points;
  • Coordinate array for lines, and srid for linestrings and polygons.

Rationale for Breaking Changes

This structural change is necessary to accommodate a major new feature in version 6: support for the Z and M dimensions.

Migration Strategy

• Version 5.1.x will contain deprecations for using the old constructor parameters.
• Version 5.1 will introduce a strict mode. When activated, longitude-one/doctrine-spatial will throw exception when you use longitude or latitude getter and setter on a Geometry. (Longitude and Latitude should only be used on Geography). By default, this mode will be deactivated.
• Version 5.1.x will also introduce factories for generating these new types (points, lines, etc.) upon release to facilitate a smooth transition.

I understand that breaking changes can be disruptive, and I'm committed to providing ample notice and support to help you migrate to the next version 6.0. Please stay tuned for more information on the release schedule and migration guides.

Alexandre

What's Changed

• Update copyrights and fix The dockerized sphinx-doc image creation process is failing #44 by @Alexandre-T in Update copyrights and fix #44 #45
• Composer upgrade feature by @Alexandre-T in Composer upgrade feature #47
• Doctrine3 feature by @Alexandre-T in Doctrine3 feature #55
• Issue Hard-code the type (string) in AbstractPoint.php #57 fixed by @Alexandre-T in Issue #57 fixed #59
• Quality tools feature by @Alexandre-T in Quality tools feature #61
• Ecologic feature by @Alexandre-T in Ecologic feature #63
• Specify return types by @Alexandre-T in Specify return types  #56
• Issue [MySQL] SpDistanceSphere missed #65 by @Alexandre-T in Issue #65 #66
• Return types mentioned by @Alexandre-T in Return types mentioned #67

Full Changelog: 4.0.0...5.0.0

---

This discussion was created from the release 5.0.0.