Mangement of Patch Submission

[cinneide]

Hi all, we're working on an extension of Mantis, called Patchy, which we use locally. The additional functionality is based around the ability for developers to submit patches (which can then be prequalified through automated testing) and managers/lead developers can subsequently approve or reject each patch. A patch consists of some description data and a single file and one patch may cover one or more bugs. Also, each bug may be related to one or more patch - a situation we found occurs for our local research fairly often.

The project is open sourced on sourceforge at http://sourceforge.net/projects/patchy and we have a live demo running in the project webspace ( http://patchy.sourceforge.net/ ) which you can log into with user/pass = guest/guest. The guest account can do all of the new features, there's no access control in it yet. We'd be grateful if anyone wants to drop in and contribute or just leave an opinion. Our goal is to integrate closely with Mantis and maybe end up with it all mature enough to be considered for inclusion into a future version of Mantis itself.

The automated testing part is done on our system through ant tasks. Whilst we only have the Patchy project on sourceforge at the moment, the autobuild/test could be an interesting OSS project in its own right in the future.

The project is pre-alpha at the moment, we're just getting in the mechanisms we need first and then we'll integrate with Mantis' authorisation mechanisms.

The current code is modified Mantis 0.19.4, we'll be migrating it to 1.0.0 as our next job (shouldn't be a big deal, right? :P )

[vboctor]

Patchy sounds like an interesting idea. I would love to have Mantis to support modules so that Patchy can become a pluggable module into Mantis without having to change the Mantis code. This would make your task easier and make it a simple task to always release a version of Patchy that works with the latest Mantis versions.

Regards,
Victor
Mantis Blog
http://www.futureware.biz/