Marek, please send communication to the mailing list. On Thu, 2006-11-16 at 11:04 +0100, [EMAIL PROTECTED] wrote: > Hi Kristis > First the question - are you going to improve the integration interface – > i.e. something that you can see at > http://www.fogcreek.com/FogBugz/docs/40/Articles/SourceControl/TortoiseSVN.html > - the links from comments & from bugs in mantis… > - bugs id are entered in a small window etc.
About the bug ids, those could be integrated, yes. http://bugzilla.mkgnu.net/show_bug.cgi?id=871 About the links from comments & from bugs, this is something that the bugtracker itself must implement. For Mantis, some autolinkification work has been done: http://bugzilla.mkgnu.net/show_bug.cgi?id=266 But it has not been merged in Mantis yet. Mantis has an open issue for this: http://bugs.mantisbt.org/view.php?id=6368 Perhaps you could request it again from the Mantis development team ? It's in bugtrackers interest in general to implement this, since it would put them ahead of the competition. Scmbug implements the integration, but the bugtrackers usually don't automatically create links out of URLs (if they were entered in comments), hence the output rendered would be practically unreadable. The apply this filtering as a security measurement from cross-site scripting attacks. > Considering incremental build I’m afraid I’m inclined toward a PHP page > integrated closely with Mantis because that solution would be the most user > friendly. Please let me know about the first question so we can move on and > create a nice SCM + Task Manager system. I'm not against a Mantis PHP page that provides a frontend for this feature. It would be a feature the Mantis bugtracker could provide, while other bugtrackers don't. But I would recommend that the page attempts to use this new Scmbug tool in the background. ***A key goal of Scmbug is to solve the integration problem once and for all***. If we were to build a command-line tool that can apply incremental builds, then all other bugtrackers could also use it: they would only have to write a user-friently webpage to use this tool. They wouldn't need to rewrite this tool from scratch. Scmbug essentially provides bugtracker "backend" support. It is intented to communicate with all bugtrackers in a generic way, so that these common SCM + Task Management tools needed will be instantly useful for all bug-tracking systems. And all SCM systems. > > There is already a lot of generic logic in > > src/lib/product/Tools/SCM_Functions.pm.in for manipulating an SCM system > > (checking in/out) and an example of this module in use in > > src/lib/product/Tools/Glue_Installer.pm.in. > > > > I would be willing to help you put together this tool. I can put a > > skeleton together, add the command-line flags you might need and > > essentially issue a VDD, You could checkout the sources from the CVS > > repository and sent patches as you make progress; I'll merge them in. > > > > How does this sound ? Thoughts ? _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
