On Tuesday, September 24, 2002, at 10:10 PM, Kean Johnston wrote:
> That last part is a good point. As for the price of disk versus
> bandwidth, I guess that's a valid argument too. But in general,
> my experience has told me that that kind of decision can come back
> to bite you, usually 5 years down the line when things are so
> entrenched that its almost impossible to deal with. Unless there is
> a compelling systematic reason why duplicates should ALWAYS exist,
> its just good practice to make their presense optional without
> causing systemic meltdown.
well, at least from what i can see, we haven't really painted ourselves
into a corner with this design. the change necessary is localized to
one portion of the code (libsvn_wc), and while you'll have to make some
pretty annoying changes there, they won't be impossible.
> If I can contribute coding cycles and work with Greg and the rest of
> this list o hash out a design to MAKE theser things optional, is
> there any reason to wait for after 1.0 if we could get it in before?
> I don't know your intended release schedule and its dinner time so
> I wont go searching :)
like most open source projects, subversion 1.0 will be released when
it's done ;-)
the milestones are only scheduled one or two out, which usually covers
a month or so. everything further is To Be Determined.
when we say something is 'post 1.0', it just means that nobody is
currently planning on holding up 1.0 to wait for it to be completed,
and that the developers who are paid to work on svn aren't going to be
devoting their cycles to it. if you've got an itch to scratch though,
don't let the fact that it isn't a '1.0' issue stop you, just be aware
that others might not be as willing to help as they otherwise would be,
since they're likely working on '1.0' issues.
garrett rooney Remember, any design flaw you're
email@example.com sufficiently snide about becomes
http://electricjellyfish.net/ a feature. -- Dan Sugalski
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Sep 25 04:37:37 2002