This project has sadly not received as much attention over the last year as in past years. We were hoping to get into a more regular release cycle, but it’s been more than a year since the last release. We are, however, hoping to get 2.2.0 out within the year.
A few maintenance releases may follow 2.2.0, but not long after that the 2.x branch of Phergie will reach EOL. Following the 2.2.0 release, efforts will be focused on Phergie 3, which will entail a number of changes we’re very excited about.
- We will be splitting the project into multiple sub-projects, following suit with projects like PHPUnit and Zend Framework. Sub-projects will have their own repositories under the umbrella of the Phergie GitHub organization.
- We will move to requiring PHP 5.3 or higher for most or all sub-projects. All new code will use PHP namespaces.
- We will make sub-projects reusable by other projects. To that end, we will be supporting use of Composer and publishing sub-projects on Packagist.
- We will integrate existing projects where possible. In particular, we’re looking at using React for the daemon portion of Phergie 3.
- We will maintain continuous integration using Travis CI.
- We will implement a low-friction process for contributing to documentation likely using either GitHub’s pages or wiki features.
We’re happy to announce the first Phergie sub-project, phergie-irc-parser. This sub-project provides a fairly fast and easy-to-use PHP-based parser for streams of data conforming to the IRC protocol. You can find the source code for it on GitHub and it is on Packagist as well.
We hope to have more announcements soon. Stay tuned!