Re: [TSVN] Re: Integration with bug tracking tools

> But I'm wondering: why does your software use such "cryptic" issue
> numbers? Seems to me that such an issue number format makes the life of
> a dev just complicated. Why not just a simple number? What does the XYZ
> stand for?

Our product has a legacy background, and runs on OS/400. Not that, that is
a reason. But anyway, the way it works is that the first 4 characters are
a project code, the next 4 are a task number, and the last 2 could be a
subtask number. There would only be embedded blanks when the project code
is less than 4 characters.

The task and subtasks can be all numbers (Base-10) or letters and numbers
(Base-36) to allow for more tasks and subtasks in the project.

So, as an example, the project code for TortoiseSVN, might be TSVN and for
Subversion might be SVN. The latter would then have an embedded blank in
the task ID. Such as SVN 0001.

The upside in this configuration is that all projects would likely use the
same base URL since the project is part of the task identifier. So there
would be less need for per version control project customization with our
product.

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 Sun Aug 22 13:23:20 2004