Skip to content

Proposal: Upgrade to PHP 8.x in a new 2.x release #33

@hidehalo

Description

@hidehalo

I see that Pull Request #28 introduces support for PHP 8.x and drop older version compatibility, which is a great step forward for the project.

To manage this transition smoothly and maintain backward compatibility for existing users, I would like to propose the following versioning strategy:

  • Release as a 2.1.x Version: The changes from PR Non-issue: Update project dependencies and use new PHP features #28, which require PHP 8.x and drop older version compatibility, should be released as a new minor version (e.g., 2.1.0). Since dropping support for older PHP versions (we already drop <7.1 on Fix deprecation warnings thrown when used with PHP 8.4 #32 ) is a breaking change, releasing a new minor version would be appropriate according to Semantic Versioning.
  • Maintain Backward Compatibility for 1.x|2.0.x Tags: The 1.x & 2.0.x branch should be maintained for users who are still on older PHP versions (e.g., PHP 5.x|7.0). This branch would only receive critical bug fixes, ensuring that existing projects do not break unexpectedly after running composer update.

This approach would provide several benefits:

  • Developers using older PHP versions can continue to use the 1.x, 2.0.x tags without disruption.
  • Projects ready to upgrade to PHP 8.x can explicitly opt-in by requiring ^2.1 in their composer.json.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions