Garrett Rooney wrote:
> Ben Collins-Sussman wrote:
>
>> At that point, we have two aggressive goals:
>>
>> 1. Get everyone to seriously hammer on the locking feature for a
>> week or so. We can fix bugs as we go, write more tests, etc.
>>
>> 2. Get /trunk stabilized for a 1.2-release branch and freeze.
>> (Immediately followed by a 1.2-beta1 tarball, as usual.)
>
> Speaking of 1.2, would anyone object to merging the Ruby branch into the
> trunk for it? The last time I played around with the Ruby bindings they
> seemed to work just fine, and assuming those who've been actively
> working on them don't have any objection to releasing them into the wild
> I don't see any reason to keep them on the branch much longer.
I came very near to +1-ing the buildsystem components of the ruby change,
but had a few minor nitpicks.
I'll try and get those sorted in the next few days.
So, overall, yes, I think we can get this into 1.2.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 19 15:20:43 2005