December 2011
5 posts
1 tag
Porting Trac Ticket Attachments to GitHub
Some of the tickets in the Agavi Trac have attachments; these attachment files need special treatment as the GitHub issue tracker itself has no support for attachments.
We’ve created a repository (agavi/trac-ticket-attachments) for this purpose and simply imported the everything from trac/attachments/tickets, which contains just a bunch of folders with the ticket ID and the attachments of...
1 tag
Testing GitHub Tickets for the Migration
One thing we’ve always put a focus on is having tickets for every change we make, and using these tickets extensively in commit messages and from other tickets so a quick svn blame on a line not only shows a description of the change, but also gives a ticket number that can be looked up on Trac to follow a discussion of the change.
On numerous occasions, I looked at a bit of code, found it...
1 tag
Moving to GitHub!
We have just begun working on migrating trac.agavi.org and svn.agavi.org to GitHub; there is whole range of things to consider, from referencing users correctly over rewriting commit messages so the correct Git commit references are included to preserving the history of tickets in their right order.
We will add more blog posts as we move along to document the process in case other projects would...
Agavi 1.0.7 released!
Agavi 1.0.7 is now available for download at www.agavi.org and through the PEAR channel.
The release contains just two minor changes over RC2, so I’ll simply quote from the final release notes:
The getCredentials() method on an Action is no longer called unconditionally (i.e. whether or not the isSecure() method returned false) but only if the Action is “secure”.
It is...
Agavi 1.0.7 RC2 released!
Agavi 1.0.7 RC2 is now available for download at www.agavi.org and through the PEAR channel.
A few minor fixes and changes have made it in since RC1; most notably, PHPUnit 3.6 should work fine now, and the Form Population Filter, when populating several forms (via an array as the value for “populate” with form IDs as keys) now gives precedence to boolean true values (so error...