>> email@example.com wrote:
>>>> I think it is important to have some sort of a wizard available to
>>>> prevent Repos Admins from making mistakes in the initial repository
>>> A wizard is nice, but it does not solve my issues. I want a better
>>> interface, which has to be built-in to Subversion.
>> Well, I understand that a wizard doesn't fix all our problems.
>> When you say "tagging interface". Do you mean that you think Subversion
>> has all the necessary support for tagging, but you just don't like the
>> way to use it. (too many arguments, URL too long, etc.)
>> Or do you think it lacks some kind of functionality? Maybe you can think
>> of situations that aren't possible at all with the current tag support
>> in subversion?
> The current Subversion scheme is difficult and too verbose for humans.
> (Whether it is 'difficult' is controversial, though.)
Well, I like the subversion tagging and branching mechanism very much.
For example, I think the CVS tagging and branching mechanism
is more difficult, because of this two-dimensional structure.
(Of course, if you are used to it...)
Not talking about important features missing,
for example version control of tags.
> For programs it is worse, because there is no built-in concept of a tag.
> So Subclipse, for example, must ask the user to find the tags for it,
> _then_ it may present the tags through the UI.
> But we are not very far from a better solution, the difficult part is
> getting everyone to agree on one. :-)
I think it is faaaaar away:
I don't know a single alternative proposal which does not have
serious problems, e.g. missing important features like version
control of tags, or a more complex UI by having two different
tagging mechanisms in parallel.
>> Btw: I don't want to crush all your arguments and tell you to quit
>> complaining, it's just that I don't have that much experience with
>> tagging used in company procedures etc. The scenarios I can come up with
>> all seem to work in subversion. So I have to have some examples before I
>> am able to see what subversion lacks. (And what subversion doesn't quite
>> lack, but still is very hard to accomplish.)
> Make a program that lists all tags for a project (e.g. given the URL of
> the 'trunk').
svn list <trunk-url>/../tags/
Personally, I prefer a repository browser like in TSVN anyway,
because there you can browse both trunk and tags itself,
and browse into tags.
> But my main motivation is not so solve something that cannot be done in
> the current scheme, but to make tags a built-in concept for Subversion.
> Then everything will fall into place.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Jul 8 13:15:29 2006