Maybe having a process (or a guarantee that a process would exist) to roll
out a repository to storage in a suitable form and then roll it into a
future updated (modified API/Code/Etc) repository would be enough for folks
to use SVN for more projects, even in its present form.
I don't know whether this would be more trouble than touching up the last
bits to go to 1.0 or not.
BobG
Perry E. Metzger wrote on 31 Dec 2002 10:57:46 -0500:
>Karl Fogel <kfogel@newton.ch.collab.net> writes:
>> Julian Fitzell <julian@beta4.com> writes:
>> > And if people are holding off until 1.0, waiting for a
>> > stable interface that they won't have to put a lot of effort into
>> > updating for each new version, then it would be misleading to release
>> > 1.0 now when we know there are significant changes that still need to
>> > be made to achieve the base set of features.
>>
>> Wow, yes, exactly -- I couldn't have said it better. Thanks for the
>> concise explanation.
>
>Some of us are waiting for an official release to use subversion in
>our projects even though we could easily accept major changes in the
>interfaces (though not incompatible changes in the repository format
>obviously). If 1.0 is more than a few months off, could a stable
>release named .8 or .9 or something be created, with a "we know it
>won't eat your code, just don't expect upgrades to be painless"
>provisio? That is to say, "this is not beta code, but don't expect the
>same sort of interface stability 1.0 would mean"...
>
>Of course, if 1.0 were to happen in two months none of this would matter.
>
>Perry
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 31 21:50:57 2002