> > We might be able to come up with a syntax in the SCM commit message > > that would allow to indicate the defect tracking back-end or > > repository to use. > > > > But maybe this not how scmbug is supposed to work today. It would be > > nice if Kristis or someone else could comment on this. > > I'm not crazy about the idea of adding in the commit message the > repository. This was suggested in the past: > > http://bugzilla.mkgnu.net/show_bug.cgi?id=775 > > > Instead I would prefer to add the capability in Scmbug to map directory > names to product names in the glue: > > http://bugzilla.mkgnu.net/show_bug.cgi?id=1169 > > The reasoning is that most likely you would separate at the SCM > directory structure which directory maps to which product and would > prefer not to have to enter the repository name during each commit (and > verify that it has been entered correctly).
[Olivier] I don't know if we can make such assumptions. What we need is both to have an easy to use system for the developer who commits code, and a flexible system for specific cases. I do not have enough knowledge on all SCM systems (front-ends as you call them in scmbug), but in Subversion, you can have "properties" at the level of the SVN repository or each folder, that could be read and indicate the defect back-end repository or product name that scmbug should use to identify the defect to work with. My understanding is that what we have today in scmbug are 2 notions: - repository (static info - daemon.conf) - product : could you explain a little more the logic behind product now, and where you would like to go with it? The idea would be to have a semi-static repository and product (using mechanics available on SCM front-ends, like SVN properties), that a developer could always overide in order to cover some corner cases (like check-in code that fixes bugs in multiple front-end repositories). I'm extremely new to scmbug - so again, don't hesitate to correct my scmbug 'vocabulary' and understanding. Thanks, Olivier. _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
