search

phacility / xhprof

XHProf is a function-level hierarchical profiler for PHP and has a simple HTML based user interface.
http://pecl.php.net/package/xhprof
Apache License 2.0
2.6k stars 925 forks source link

project status #85

Closed carlwgeorge closed 3 years ago

carlwgeorge commented 8 years ago

I am a core maintainer for the IUS project. We received a request to create RPM packages for this module. What is the current status of this project? Here are the things that I can observe that concern me from a packaging standpoint.

epriestley commented 8 years ago

This is the official codebase, in the sense that facebook/xhprof moved here. We took it over from Facebook when they cleaned up some projects they were no longer maintaining from facebook/. Since Facebook switched from Zend PHP to HHVM some time ago, it no longer made sense for them to continue committing resources to maintaining this project. They have similar replacement code in HHVM which works with that runtime.

We do not control the PECL extension. I've had some discussion with people with more familiarity than I have about PECL and they asserted that PECL extensions may not have CLAs. This project has always had a CLA (both under us, and originally under Facebook) so it may have been added to PECL in error. We do not plan to remove the CLA, and it seems like updating the PECL extension is at an impasse. (As a possible way forward, I've suggested that the PECL extension be deprecated and pointed at some new extension, which could be an upstream-tracking fork of this project without a CLA -- although that would somewhat defeat the purpose of the "no CLAs" rule -- or some other fork of this project, but this hasn't moved forward.)

The 0.9.4 vs 0.9.2 is some sort of error, but I haven't tried to hunt it down since it seems immaterial given that PECL is essentially frozen.

We do not monitor bugs.php.net, so issues should be reported here.

We are maintaining this extension, but we have limited resources and its development is not a priority for us, so you should expect glacially slow responses from the upstream. There are several forks available which may be more actively maintained, and might be better practical candidates for packaging. I'm not familiar enough with them to recommend one in particular.

carlwgeorge commented 8 years ago

Thanks for the quick response @epriestley. If the extension is still maintained (even on a limited basis), we can package it. Our primary requirements are to have a place to report bugs and to have a release that is considered "stable" by the upstream. Would you consider tagging a new stable release in GitHub? Being uploaded to PECL would be nice but is not a strict requirement.

zsprackett commented 7 years ago

bump, @epriestley any chance you would be willing to tag a stable release? getting this packaged would be really useful.

williamdes commented 3 years ago

:ping_pong: After 5 years stale.

Anyone interested about the project progress should comment on https://github.com/code-lts/welcome/issues/6

The pecl page doesn't have any releases that are marked stable. The most recent beta release was 0.9.4 on 2013-09-30.

The pecl page is now okay

epriestley commented 3 years ago

There is no more recent stable release.

williamdes commented 3 years ago

Would you agree to transfer this repository to the @code-lts org ?

epriestley commented 3 years ago

No. I'd encourage you to fork it (or work with one of the existing forks) if you aren't satisfied with how it is currently being maintained.

williamdes commented 3 years ago

No. I'd encourage you to fork it (or work with one of the existing forks) if you aren't satisfied with how it is currently being maintained.

Thank you for the update, could you give me an official status of the project ? Are you willing to close all the issues/PRs on this project ?

epriestley commented 3 years ago

The official status of this project is explained earlier in this thread. There have been no changes since that comment in 2016.

https://github.com/phacility/xhprof/issues/85#issuecomment-196489773