[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN Model and 1.5 release hoohah

From: Gavin 'Beau' Baumanis <gavin_at_thespidernet.com>
Date: Sat, 01 Mar 2008 21:54:58 +1100

Hi Everyone,

I started writing this email a little while back when I first started
reading the thread,
Subversion 1.5, Technology Preview - started by EPG.

But having read it a few times (the thread and my email - I still
couldn't make up my mind as to what "model" you were all talking about -
with respect to it being too restrictive to development.
Was is the architecture / application model - or the release model? - I
don't know... and so for a while I sat on releasing my email - so as to
not to come across as some newbie with absolutely no idea.

Mind you, I have decided that I am pretty comfortable with the tag of
newbie - since I am completely new... and quite simply do have no idea.
None the less, despite not knowing exactly what model you were all
talking about - I think my question is still valid none the less.
Please find my original email below.

Hi Everyone,

Let me just start with;
I am pretty naive as to the inner working of SVN (and the process for
getting development done).

I have at best intermediate skills as a SVN user and even less with
respect to administration and I certainly understand the business
realities of my next line too - so the cost (manpower and money) isn't
lost on me at all...

But surely, if the 'model' is broken - should it not just be fixed? - or
even rewritten outright?

I have been reading through the archive recently (working on my quest to
collate the 'obliterate' use-cases) and I have noticed a few times that
the explanation is along the lines of;
"That's just the way it is".
Sure there is a valid reason for it being that way;
* Too hard to correct,
* Too time consuming and
* Quite often simply just not technically possible).

(and I am leaving out the requests, where a user's request could be
successfully performed with existing commands and some education about SVN).

But if a user has a solid request, and the developers also agree the
request is a solid one too;
Then shouldn't a response like, "We can do it because of the current
design - work around it by doing 'A', and 'B'.", trigger something more

It has been such a long time since the original design was completed.
The use-cases are now more complex and varied - and move outwards from
the original core design, in ways no one ever though of two years ago -
let alone from the original design of SVN as a whole.

Thus, my (naive) question is;
Is it time to re-design the SVN model and "fix" the underlying gotchyas
that stop some of the ideas from even getting off the ground?

Gavin Baumanis
The Spidernet Web Design
W: http://www.thespidernet.com
E: gavinb_at_thespidernet.com
P: 03 9750-6313 (+61 39750 6313)
M: 0438 545 586 (+61 438 545 586)

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org

Received on 2008-03-01 16:19:58 CET

This is an archived mail posted to the Subversion Dev mailing list.