[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Avoiding blocking the UI while running hook scripts?

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: Tue, 22 Apr 2008 08:54:32 +0200

Hi Roger,

On 22/04/2008, Roger Lipscombe <roger_at_differentpla.net> wrote:
<snip>
> The user story I'm attempting to solve here is this one:
>
> 1. Marvin the manager assigns a ticket or task to Dave, the developer,
> using the issue-tracking or task-management software (we use
> TargetProcess, I use Trac for my personal projects).
> 2. Dave looks at his list of tasks using the issue-tracking software's
> front end (i.e. a web-dashboard). He picks something to work on this
> morning.
> 3. Dave fires up Visual Studio; hacks on some code; does some work
> toward the task.
> 4. Dave brings up TSVN's commit dialog. He types in a comment that lists:
> a) The ticket/task number of what he's been working on.
> b) Some comments about what he's changed.
> c) How long he's spent working on the task.
> d) How long he thinks is remaining.
> 5. He clicks OK, and his changes are committed to the repository.
> 6. TargetProcess monitors the SVN repository, watching for commits. It
> sees Dave's commit message, extracts the information from it, and
> updates the task, by adding "time" to it.
> 7. Marvin looks in TargetProcess, and can monitor the project's progress.
>
> As it stands, TSVN supports (most of) this admirably. For example, with
> the Trac integration, I can put "See #43" or "Fixes #99" somewhere in
> the commit message, and Trac's post-commit hook will update the tickets
> accordingly.
>
> However:
> 1. Dave has to keep the issue-tracker front-end open in order to look up
> the ticket numbers.
> 2. Some issue trackers want more information (e.g. time spent, time
> remaining), and it needs to be formatted more rigidly. For example,
> TargetProcess wants something like (from memory): "task:66 spent:3
> remaining:2 comment:Move strings to resource files"
>

Why not reverse the way Dave works: let him update the issue via the
issue tracker and then let the tracker start the commit with a
pre-formatted commit message (put the burden of accessing (T)SVN on
the issue tracker, not the other way around?

-- 
Regards,
Jean-Marc
----------------
    ___
   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-04-22 08:54:40 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.