There are a few reasons for this transfer:

• A new core team will be given merge rights to streamline acceptance of contributions where it was previously limited by the availability of a single developer.
• Eventually, plugins and other sub-projects can be split off into their own repositories within the same organization to be developed independently from the main project and to allow more fine-grained grants of merge rights.

Any pull requests and issues should be directed to the transferred repository. Any existing clones of the original repository will need to have their upstream remotes updated to point to the new location. This can be done using the following command:

git remote set-url upstream git://github.com/phergie/phergie.git

Any questions about this change can be directed to the #phergie IRC channel on Freenode or in a comment on this post.

1. Human error – In an effort to push the release out more quickly to replace the existing Phergie 1.x installation on Freenode with a 2.x instance, this issue was simply overlooked and somehow didn’t present itself distinctly during rudimentary testing. This was a big mistake on our part and we apologize to any affected users.
2. Lack of sufficient unit testing – This is something we’re working on. However, the problem was actually with two Phergie core components that had full code coverage. This shows that, while code coverage can be useful to expose blocks of code that are definitely not covered by any tests, don’t assume code is fully covered simply because code coverage says it is.
3. Unexpected behavior – What appears to be a bug in PHP itself, specifically in the FilterIterator class, contributed to the problem. Oddly, this class also appears to have full code coverage, affirming the related point above.

For those users affected, there are two options for dealing with this issue pending the next release.

1. Downgrade to Phergie 2.0.2 – Not ideal, but that release was relatively stable.
2. Patch 2.0.3 – The patch is in the git repository if you’d like to apply the patch to fix the issue yourself.
3. Run Phergie bleeding edge – This is done by cloning the git repository, placing your settings file on the same level as the Phergie directory, and running the phergie.php script there.

We’re hoping to make another release within the next couple of weeks.

What: The Phergie Hackathon

Where: The #phergie channel of the Freenode IRC network

When: Saturday, June 19 from 10 AM CDT till the last person leaves

Why: We’re gearing up for a 2.0.3 release and we’re looking to knock out as many bugs as we can that currently block us from replacing the old Phergie 1.x instance currently running on Freenode with a 2.x instance.

How: Just show up in the IRC channel, pick a ticket from the laundry list, and start hacking. Feel free to post any questions you may have to the channel. If you want to hit the ground running on the day of the Hackathon, decide what ticket you’d like to work on and take a look at the developer docs and source code beforehand.

Hope to see you there!