Mark Phippard wrote:
[snip]
>
> This is what I think svn could do:
>
> 1) Elevate bug ID to a full-fledged citizen, like the log
> message. A lot
> of the validation and configuration for that could then be part of
> Subversion. This seems unlikely they will do. Compromise seemed
> to be to
> allow revprops to be part of the commit. That was the Bug ID I
> referenced.
>
> 2) Configuration. Perhaps do something to help us with the config
> options. The main thing would be to define config in repository and have
> that pushed to client. Then we could just piggy-back on that. I do not
> know how likely that is.
>
> I wonder if revprops on rev 0 could somehow be stored in the WC? Perhaps
> that would be how they would do it?
>
> Otherwise, I think all that svn could really do would be to publicize the
> "conventions" we adopt and encourage other GUI clients to do the same.
>
Has anyone looked at the tigris 'subissue' project?
Obviously what is proposed in this thread is trying to avoid tying in to a
particular bug tracking system. Also subissue stores its bug track
information in subversion folders as part of the commit of the changed
code - an option probably not open to other bugtrack systems. However they
also raise the issue of how to create an atomic commit - although don't give
any solutions on the website.
Perhaps some discussions with them and a united front would assist in
persuading the subversion team to reserve the necessary configuration files.
Vince
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 18 11:31:54 2004