Cool. Just a few comments.
1) Weren't there some issues with using ':' property names? I thought
they were discouraging using that for some reason. I think it has to do
with sending them over DAV. I do think it was fixed though.
2) Could you explain more how you have integrated this into the history,
such as log displays? For example, when does the URL come into play? Are
you just parsing the log messages to get the bugID?
3) While I think your reasoning on revision properties is somewhat solid,
I still see no reason not to add the feature, especially if it was off by
default and required some properties to turn it on. The main reason for
revision properties was that it seemed like it would make #2 easier to do
consistently across clients. Perhaps that is not the case. I also think
it would open the door someday to be able to query the repository by
revision properties. Currently you cannot do this, but the idea has been
floated as being desirable. In a SQL repository this would probably be
easy to do.
4) RegEx. I do not think it would be too huge a problem if there were
inconsistencies as long as the way it worked was documented. I was
wondering whether there were libraries available though. I do not know
RegEx very well myself, but I would assume that the RefEx to validate a bug
ID would be fairly simple and likely to be consistent across
implementations. Idle speculation though.
5) If not RegEx, another built in validation could be minimum and maximum
characters.
6) My Bug ID's can sometimes have embedded blanks. Will that be OK in
your system? For example might be XYZ 0001.
I look forward to trying this, when do you think there will be a new build
available with this in it?
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Aug 21 20:56:14 2004