That's a configuration choice on your development model. You can certainly choose to integrate with issue-tracking that way. If you wanted to, you could have your personal issue-tracker hosted locally for local development, and use Scmbug hooks.
All these are choices you can make, and Scmbug should not get in your way. Scmbug should, however, support other development models besides the one just described. On Fri, 2010-02-12 at 23:51 +0300, Иванов Михаил wrote: > hallo once again, > > A little follow-up to the previous message. Actually when I do not have > permanent network connection to scmbug server host (and in my case that > happens) I still want to make commits to my local repository - and have > them processed by scmbug later when communication is available. In this > case it makes more sense to not to have hooks in local repository and > delegate all handling of interaction with bugzilla to remote one. > > Best regards,
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
