[GH-ISSUE #53] What PHP version should we support? #20

New issue

Closed

opened 2026-03-04 23:23:47 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 23:23:47 +03:00

Owner

Originally created by @samuelwilliams on GitHub (Sep 4, 2018).
Original GitHub issue: https://github.com/yswery/PHP-DNS-SERVER/issues/53

The composer and travis files currently indicate support for PHP 5.5 which has reached end-of-life. PHP 5.6 will reach end-of-life at the end of this year. Should we change the minimum requirements to PHP 5.6 with a view to update again to PHP 7.2 at the end of the year?

This also affects the PHPUnit testing framework version.

[http://php.net/supported-versions.php](PHP Version Support)

Originally created by @samuelwilliams on GitHub (Sep 4, 2018). Original GitHub issue: https://github.com/yswery/PHP-DNS-SERVER/issues/53 The composer and travis files currently indicate support for PHP 5.5 which has reached end-of-life. PHP 5.6 will reach end-of-life at the end of this year. Should we change the minimum requirements to PHP 5.6 with a view to update again to PHP 7.2 at the end of the year? This also affects the PHPUnit testing framework version. [http://php.net/supported-versions.php](PHP Version Support)

kerem closed this issue

2026-03-04 23:23:47 +03:00

kerem commented

2026-03-04 23:23:48 +03:00

Author

Owner

@ivanstan commented on GitHub (Sep 7, 2018):

Personally, I wouldn't bother with php 5.6, in only four months it will be over for php 5.6. Besides we would loose some good type hinting with this backward compatibility

@ivanstan commented on GitHub (Sep 7, 2018): Personally, I wouldn't bother with php 5.6, in only four months it will be over for php 5.6. Besides we would loose some good type hinting with this backward compatibility

kerem commented

2026-03-04 23:23:48 +03:00

Author

Owner

@samuelwilliams commented on GitHub (Sep 7, 2018):

I agree with that position. I think this is where tagging releases would prove useful as it allows us to set a support cut-off.

@samuelwilliams commented on GitHub (Sep 7, 2018): I agree with that position. I think this is where tagging releases would prove useful as it allows us to set a support cut-off.

kerem commented

2026-03-04 23:23:48 +03:00

Author

Owner

@ivanstan commented on GitHub (Sep 8, 2018):

I'd like to suggest git flow approach for code management.

Branches:

develop
release
and feature branches prefixed with feature
feature/feature-name-tests

@ivanstan commented on GitHub (Sep 8, 2018): I'd like to suggest git flow approach for code management. Branches: - develop - release and feature branches prefixed with `feature` - feature/feature-name-tests

kerem referenced this issue

2026-03-04 23:24:03 +03:00

[PR #20] [MERGED] Improved test configuration. #51