Skip to content

Conversation

hopeseekr
Copy link

@hopeseekr hopeseekr commented May 15, 2019

Only support PHP 5.6 and later.


This change is Reviewable

],
"require": {
"php": ">=5.0.0"
"php": ">=5.6"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it proper to support php-5.6 version at least?

The php-5.6 and php-7.0 are unmaintained on official PHP team.

And the php-7.0 has been release for about three years.

If we want to keep the package e compatibility, I think we can let the package require php-7.0 version at least.

Copy link
Author

@hopeseekr hopeseekr May 15, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See? I debated that, too...

I figured if it was going from, literally, 5.0.0, maybe it'll be too much of a shock to active users, especially on legacy sites?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK but. I just started thinking... since this will be in effect a new project, I officially hard forked it to phpexpertsinc/chromephp and will be releasing a new composer package. It will definitely target PHP 7.0.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can release two versions.

One is about supporting PHP 5.6.

Another one is about supporting PHP 7.1+.

This can be compatible with PHP 5 users.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right.

I think releasing the new version is the proper way because original package has been inactive for about long time.

@hopeseekr
Copy link
Author

Everythign in this PR is in PR #74.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants