Ben Collins-Sussman <sussman@collab.net> writes:
> issues@subversion.tigris.org writes:
>
> > + ------- Additional Comments From cmpilato@tigris.org 2003-03-19 11:21 PST
> > + Okay, I've decided to propogate this functionality in three stages,
> > + with a couple of milestones between each stage:
>
> Now I'm confused. Mike, you just detailed three stages of gradual
> feature rollout, extending into releases 0.22 and 0.24.
>
> But didn't we just establish a policy (in HACKING) about clients and
> servers only needing to be compatible within one release?
>
> I don't understand. If 0.20 clients and servers know how to recognize
> and handle the new xml attribute, why can't you just finish the
> rollout completely in 0.21?
If I finish the rollout in 0.21, then 0.21 clients that put binary
properties into 0.20 servers will not be able to get them out again.
Checkouts will fail, chaos ensues. The solution is the three-step
process I detailed, which disallows the addition of XML properties
over ra-dav until the server is fully capable of transmitting them.
And why don't I turn on the server transmission of binary properties
now? Because then a 0.20 server sending bin-props to a 0.19 client
will cause the client to store base64'd versions of the properties in
the working copy instead of the real prop value.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 19 21:38:02 2003