The Patchy Server News

Version 0.0.4 has been released for download in the Files section. The roadmap file has also been updated and released for download. The latest commits to the SVN repository reflect the code changes, its getting there. The live demo will be updated to version 0.0.4, with new users to test the access control, shortly.

With subversion available for SF projects, we now have the code available at https://svn.sourceforge.net/svnroot/patchy/patchy/trunk/ and should shortly have it migrated to version 1.0 of Mantis. Once that's done we'll release the project as both a complete modified version of Mantis and also as a set of patches to accomodate people with their own customisations of Mantis.

The project documentation (currently just the roadmap doc) is also in SVN in both latex and pdf format at https://svn.sourceforge.net/svnroot/patchy/docs/trunk/
Many thanks to SF for providing the SVN repository!

A document providing an overview of the Patchy functionality and project milestones is available for download in the Files section (http://sourceforge.net/project/showfiles.php?group_id=159384). If you think you would like to help with these goals, please join in!

There's a new release in the files section, version 0.0.3, with the "Edit Patch" page completed. The two most immediete tasks are now a) Add access control to the various patch submission features and b) make it prettier!
The live demo, http://patchy.sourceforge.net/patchy/ (user: guest, pass: guest) has been updated with the latest code changes.

A new version is available in the Files section, this fixes two problems with the first "release".
1) Some out of date sql had crept in but is now fixed.
2) The contructor for PatchObject.php was a php5 constructor. It's now changed to work for older versions of Php.

So now the live demo at http://patchy.sourceforge.net/ (user: guest, pass: guest) really is live! This step has ironed out a lot of the teething problems with getting the project set up on sourceforge and learning how to use the features correctly. Now we can get back to the coding.

Just a reminder, you can't create any accounts on the live demo Patchy installation since it can't email you for confirmation. You must use the guest account (guest/guest).
We've set up a test project with guest added as a developer (sorry if you tried to use it before, this was completed today!) so you can create issues and submit patches etc.

The first release from the project (version 0.0.1) is now available at https://sourceforge.net/project/showfiles.php?group_id=159384
and contains the php code currently running as the live demo at http://patchy.sourceforge.net/patchy/
At present this is the only way to get the code for the project, we've had lots of trouble with the CVS server so we're waiting for the SVN service to become available for easier access.

We have a live demo of Patchy in its current form running in the project web space (http://patchy.sourceforge.net/patchy/) where everyone can have a look a the system running.

The particular features that we've added are the "Submit Patch" button when viewing an issue, the "View Patches" menu item on the top of each page and the approve/reject functionality in "View Patches" and when viewing each patch individually.
The "Edit Patch" page is yet to be completed.... read more

All of the mechanisms for submitting a patch, viewing patches and approving/rejecting patches are just about done, all that remains is some DB work on an "edit patch" page. Once this is complete, we will put up a live demo on the project's home page. Also in the works is some documentation explaining exactly what our plans are for this. We're waiting for the SVN server access to put the code up, I'll try to get an update into CVS in the meantime.

The system (in CVS) now accepts patches correctly and provides the means to view and download them. The "Patch Information" field when and issue is viewed shows a link to the patch(es) for that issue and a new item "View All Patches" in the top menu shows a list of all the patches sorted by approval status. Next up is the more detailed editting and manual moderation of the status of patches, including the introduction of a "rejected" status and mechanism. Blind optimism caused these to be left out so far!

We're set up on Sourceforge, and the first chunk of code is in. This includes buttons for submitting patches on the issue pages and links to download existing ones. The next step is pages to view and edit patches, and then the approval lists. Concurrently, we're working on ant tasks for automated testing in our own environment, but we're not sure as yet how much can be generalised. We'll add hooks at the very least.