Steve King <email@example.com> wrote on 07/27/2004 12:04:39 PM:
> I was contacted by some guys who want to make TSVN integrate into their
> bugtracking software. But whatever idea we come up with ends in the
> missing feature of server-dictated config options:
> - Adding the bug-ID/Issue-Number to the log message in a format so that
> the bugtracker can parse it. Since each project can have a different
> bugtracker this format should be stored somehow in a server config.
> - Add the bug-ID/Issue-number as a special property to each file of a
> commit (before the actual commit). The format of that property could
> simply be the bug-ID/Issue-number, but I'd like it better configurable
> per project.
> - Starting the browser with the bug-ID(s) stored in the property of a
> file and the bugtracker-URL. To prevent having the user enter the
> bugtracker-URL of each project manually this should be stored on the
> server too.
> So you can see: all these informations/options should best be stored on
> a per-project basis, and that would require server-dictated config
> Just some thought for what this would be useful for too.
I want to do the same thing, I have also considered all of the options you
listed. I was thinking of using a pre-commit hook to validate the bug ID
in the log message and maybe a post-commit hook to turn it into a revision
property. That would make the information more queryable, and perhaps
someday with a SQL back-end, very queryable. (Is queryable a word?)
I doubt this idea will go over well, but I would really like to see
Subversion elevate bug-ID/issue-number to a full-fledged revision
property, like log or author so that it would just be another argument of
the command line. Like:
svn ci -m "Checking in changes" -id "ABC123" URL
Perhaps a configuration setting (which someday will be server controlled)
could provide a regex to validate the ID, or not require one at all.
I have experimented with hacking the Tortoise and Subclipse UI to add this
to the commit dialogs and it looks like it would be fairly easy to do. The
problem is that it then only works in those UI's and the command line does
not enforce it.
Does anyone think this would ever make a good Subversion feature? Doesn't
everyone use some kind of bug tracking system these days? Why not make it
a full-fledged part of the UI?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jul 27 20:15:29 2004