> Max Bowsher wrote:
>> Seemingly stable or not, it's still just a candidate patch.
>> You've backed yourself into an unpleasant corner here, relying on a
>> that is still quite some way from integration.
>> Even worse, you are using a branch based on trunk, which we do NOT
>> recommend for production use.
> Well, I had patches off the latest stable release, but was asked to work
> trunk - now I read that basing on trunk is not recommended :-)
Not recommended for users.
Developers need to work off trunk.
> Saulius, I'll send you a patch tomorrow that applies to the current trunk.
> Apply this to a trunk-checkout, and you'll be fine.
> (That's what my patches/ directory was for, you know =-/)
But we shouldn't be encouraging people to use trunk for production purposes.
Which was the main reason I removed patches/ in the first place.
> And BTW, how about merging at the text-time-branch for 1.2 or 1.2.1? If
> everybody who ever contacted me about this uses my branch, it should be
> much tested by now.
The main problem is in the way you have presented this change, going very
much against the conventions of the project. We want Subversion to be
designed, not just grown in an ad-hoc manner. I have seen that someone else
has already asked you to post information on the *design* of the feature to
dev@. The point is, we want to agree on the design *independent* of the
code. Unless you summarize the design, someone will have to reverse-engineer
a design description from your code - which takes time and effort - and most
committers time and effort is focused on getting 1.2 out the door right now.
And 1.2.1, etc., would be patch releases - bugfix only, no new features.
> (Same for the full meta-data-versioning; it has changes in the same
> as text-time, only the property names and uses are different).
No way, owner-group-mode is *much* more complicated. For instance, does it
protect the text-base file similarly?
> And for the request about a design-document for my branches: does the old
> doc-patch at
> help? I know that is has not much details, but that's how it works.
> (Simple substitution of property values as commit/import time, using them
Ah, so you have seen that email.
It helps a bit, but leaves much unanswered.
For example... does it cover switch too? What value do you use with "svn
propset"? And posting it as a brief mention in an unrelated mail to users@
is no good - people on dev@ need to see it.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Mar 28 12:35:18 2005