SteveKing <steveking@gmx.ch> wrote:
>
> We're not talking about the list of projects but the list of open
> issues! And even in open source projects, _some_ of the issues are not
> publicly available for security reasons (at least not until they're
> fixed)!
Let me clarify. "Project" = "Open Issue" for my company. Just a
terminology thing. Developers only work on assigned projects which will
have project IDs autogenerated when they start working on them.
Also, I was just giving you a data point for my company. I fully understand
that other companies will be different as will open source projects. I just
wanted to clarify that the list of assigned tasks/projects/issues may not
always be secret and require authentication internally for a corporate use
of subversion. Yes, we may not publically release the details until we have
a fix, but we don't make an attempt to hide the details frmo other
developers internal to the company.
If my opinion counts for anything, I am more in favor of an extension of the
existing seperate text box for issue numbers (vs autocomplete in the log
message). I would also love to see a configuration option (via property,
etc) that disallows free text typing in the issue text box and only allows
them to choose from the list. We have had many problems with typos being
made and then the wrong issue/project getting associated with a commit
without any obvious error. By limiting developers to a finite set of
issue/project numbers we could really clean this up.
Anyway, I'm just excited to see the ideas being discussed, and we can
probably come up with a solution that will work with our internally
developed project managment system no matter what solution you settle on (as
long as you don't make us implement DAV :). Thanks for the hard work!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Feb 22 20:24:56 2005