Peter Mounce wrote:
> 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.
The problem with that approach is the different time formats out there.
Depending on the locale, the time format can differ a lot and it would
be very hard to parse the time and also to really get that parsed string
into a real time object because of that.
Just parsing a time string could be left to the repository admin who
would be responsible to create the regex string. But having TSVN
actually make sense of that string is much harder and will lead to
problems (e.g. project in english, but user has other OS).
> 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
And because of that gibberish, I don't like that idea. It's also much
harder to reliably parse those named groups.
If this should be implemented, then as a separate regex and separate
property. Also because we need to be backward compatible.
>>> 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?
If that's ok with users, I'm also fine with it.
>>> 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.
I'm still thinking of why this has to be implemented in TSVN: parsing
the log message must be done in a hook script anyway.
All TSVN could do here is
* show a separate column in the log dialog with the time string (is that
really useful?)
* highlight the time string while the user writes the log message
Maybe another property bugtraq:warnifnotimeset ?
But that's all I can think of now. Not really enough I think. With the
bugtraq: props right now, TSVN at least can provide links to the
issuetracker - this is really a benefit in TSVN which can't be done with
custom properties and hook scripts.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Dec 6 20:00:08 2006