You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Garrett Rooney <ro...@electricjellyfish.net> on 2006/08/22 21:39:25 UTC
Re: svn commit: r21209 - branches/1.4.x
On 8/22/06, maxb@tigris.org <ma...@tigris.org> wrote:
> + * r21207
> + Rename svnadmin create's '--no-svndiff1' to '--pre-1.4-compatible'.
> + Justification:
> + --no-svndiff1 is poor user interface.
> + Votes:
> + +1: maxb
For what it's worth, I think it's absurd to be trying to put in UI
changes at this point in a release cycle, especially when it's an
interface that almost nobody is ever going to care about. All this
can possibly do is stretch out the release cycle with virtually no
gain.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: r21209 - branches/1.4.x
Posted by Max Bowsher <ma...@ukf.net>.
Branko Čibej wrote:
>
> I think this renaming is wrong anyway. Whenever there's a potential
> compatibility issue, we always do feature tests, not version tests.
> That's true of the autoconf stuff (mostly ...), protocol negotiation,
> etc. etc. So --no-svndiff1 is actually more correct in this respect,
> even though it may look slightly more confusing to the user.
I feel that the above reasoning is logically flawed: you cannot take a
best-practice tenet about how build-systems should adapt to platform
incompatibilities, and apply it to UI design. The two fields are
scarcely related - that feature tests are appropriate for one does not
infer that they are appropriate to the other.
A vital quality of a UI is understandability for the user. Therefore, if
--no-svndiff1 is more confusing that the alternative, it is not correct.
> For example, --pre-1.4-compatible could well mean "don't create BDB
> repositories if you're linked with BDB-4.4".
The above is not sensible: the BDB version is in no way intrinsic to the
Subversion version. You could just as well have a Subversion 1.3 linked
to BDB 4.2 and a Subversion 1.4 linked to BDB 4.3, producing a
compatibility barrier even though BDB 4.4 is not involved.
> It's not as obviously mnemonic as you think.
It's pretty obvious, and more obvious than --no-svndiff1, I think.
Thankyou for your comments, but it sounds to me that your objections
stem more from frustration at another release delay than with the
details of the change itself. I sympathize - I feel annoyed by the delay
too, but having noticed this issue, it couldn't in good conscience
pretend to forget about it, deliberately lowering the release quality to
get it out faster.
Max.
Re: svn commit: r21209 - branches/1.4.x
Posted by Branko Čibej <br...@xbc.nu>.
Max Bowsher wrote:
> Justin Erenkrantz wrote:
>
>> On 8/22/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>>
>>> For what it's worth, I think it's absurd to be trying to put in UI
>>> changes at this point in a release cycle, especially when it's an
>>> interface that almost nobody is ever going to care about. All this
>>> can possibly do is stretch out the release cycle with virtually no
>>> gain.
>>>
>
> See my mail under separate subject line "r21207 (Renaming --no-svndiff1
> to --pre-1.4-compatible)".
>
>
>
>> At the very least, I believe that these changes should have been
>> discussed on-list prior to being committed. -- justin
>>
>
> I've only committed them to trunk. Reverting them, whilst not a course
> I'd prefer to take, remains a possibility - I've not committed us to any
> permanent course of action.
>
> In fact, I dearly hope that these changes will *not* be controversial -
> they are, after all, a simple renaming, to a name which I feel is
> better, for distinct reasons. Of course, I'm a little too cynical to
> believe that my hope will prove real.
>
> I acted as I did to stimulate a quick resolution to this situation, to
> minimize release delay as far as humanly possible.
>
I think this renaming is wrong anyway. Whenever there's a potential
compatibility issue, we always do feature tests, not version tests.
That's true of the autoconf stuff (mostly ...), protocol negotiation,
etc. etc. So --no-svndiff1 is actually more correct in this respect,
even though it may look slightly more confusing to the user. For
example, --pre-1.4-compatible could well mean "don't create BDB
repositories if you're linked with BDB-4.4". It's not as obviously
mnemonic as you think.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: r21209 - branches/1.4.x
Posted by Max Bowsher <ma...@ukf.net>.
Justin Erenkrantz wrote:
> On 8/22/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>> For what it's worth, I think it's absurd to be trying to put in UI
>> changes at this point in a release cycle, especially when it's an
>> interface that almost nobody is ever going to care about. All this
>> can possibly do is stretch out the release cycle with virtually no
>> gain.
See my mail under separate subject line "r21207 (Renaming --no-svndiff1
to --pre-1.4-compatible)".
> At the very least, I believe that these changes should have been
> discussed on-list prior to being committed. -- justin
I've only committed them to trunk. Reverting them, whilst not a course
I'd prefer to take, remains a possibility - I've not committed us to any
permanent course of action.
In fact, I dearly hope that these changes will *not* be controversial -
they are, after all, a simple renaming, to a name which I feel is
better, for distinct reasons. Of course, I'm a little too cynical to
believe that my hope will prove real.
I acted as I did to stimulate a quick resolution to this situation, to
minimize release delay as far as humanly possible.
Max.
Re: svn commit: r21209 - branches/1.4.x
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 8/22/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> For what it's worth, I think it's absurd to be trying to put in UI
> changes at this point in a release cycle, especially when it's an
> interface that almost nobody is ever going to care about. All this
> can possibly do is stretch out the release cycle with virtually no
> gain.
At the very least, I believe that these changes should have been
discussed on-list prior to being committed. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org