Stephan wrote:
>> While I have a pretty good idea on how the extended log window would
>> look like (an additional column showing the time), I have no idea
>> how/where that information should be shown in the statistics dialog:
>> there's nothing in there which shows the bug ID's now.
I was thinking about a graph with a line per user against time showing time-spent,
and then at each point (perhaps only when hovering over a line on the chart
or legend) display a number indicating the commits for that point's time-period
(depending on the granularity of the graph).
You could measure commits per day, for example; I don't know whether that's
a useful metric, however - I only know it would be interesting to me.
>> If the time-spent (ts) is on the same line or even intermixed with
>> the actual bug ID, then we'd have to catch this with the
>> bugtraq:logregex. But it it's standalone, then we'd have to introduce
>> a separate regex property.
I was hoping that it would be possible to introduce a regex that captures
(optional) named groups. For example:
[Ii]ssues?:?(\s*(,|and)?\s*#\d+)+
(\d+)
is the one I use at the moment (you will recognise it ;-) ).
If that could be changed to (for example)
[Ii]ssues?:?(\s*(,|and)?\#\d+(\((\d+h)?\s*(\d+m)\))?)+
(\((\d{0,2}h)*?\s*(\d{0,2}m)?\))?
(bloody hell, that's gibberish, reading it! :-) ) then that could capture
first the issue groupings, then split those up into issue number and time-spent.
It would be nice to validate time spent (so, no more than 60 minutes, etc),
but not really essential.
>> Also, how should we indicate this in the commit dialog? We already
>> use a different color, bold and italic letters.
I think it can just be a part of the existing highlight, if it's made to
be part of an issue-grouping in the commit dialog?
>> How many bug tracking systems out there have the ability to specify a
>> time?
Many. Seriously. Off the top of my head:
FogBugz
Gemini
OnTime
Trac (although, it's not done yet)
Mantis?
JIRA
...
>> If it's just the one you're using, I don't think it's worth
>> introducing this in TSVN, because as you already noticed you could
>> introduce your very own property (e.g. gemini:timeregex) and do the
>> rest from hook scripts.
Yeah, I know - but it would be lovely if the integration went all the way
around. The hope, here anyway, is to get to the point where when we do a
commit, the log message and the list of files changed, and the time taken
will all be automatically hooked into our issue tracking (it exposes a web-service
for exactly this sort of thing) - thus making it really easy for a developer
to do, all in one place. At the moment, he has to first commit, then hopefully
be diligent and update the issue he's committing against to reflect what
he did, etc. Project management here is not going to read subversion commit
logs to find out what's going on in the project - and nor should they, really;
that's what the issue-tracker is supposed to be for. Therefore we need developers
to update the issue tracker, and rather than introduce software-enforced
rules, we would prefer it if it were so incredibly easy to do, people just
did it in the same operation as writing a commit log message.
Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Dec 5 11:27:46 2006