Re: 1.3 feature question

On Aug 5, 2005, at 9:01 AM, Miha Vitorovic wrote:

> Ben Collins-Sussman <sussman@collab.net> wrote on 05.08.2005 15:05:43:
>
>
>> There's no voting process going on for "which feature goes into
>> 1.3". Lots of people are working on new features on /trunk. At some
>> point, we decide that /trunk has enough new features to justify a 1.3
>> release. Then we branch /trunk to /branches/1.3.x and let the branch
>> stabilize.
>>
>>
>
> Wasn't there a discussion somewhere about what to do next - true
> renames,
> merge tracking,... ? I remember reading something about that.
>
> But I like this approach, it must be cool to develop that way.

For those not on the dev@ list:

True renames are being worked on, but only in the repository API (it
involves a schema change.) Dunno when it will be done, but even when
it is, it won't be immediately obvious to users. It will take a long
while to get the rest of Subversion to start using the new API.

I'm working on getting svnserve to log accesses and high-level client
operations, as well as improving mod_dav_svn's logging.

Someone else is working on fixing the broken "svn checkout -N"
problem. He wants a UI which allows users to declare which
subdirectories they do/don't want, and then 'svn up' will honor the
stickiness.

We have a bunch of Summer of Code students working on new features:

   * path-based authorization for svnserve (similar to what
mod_dav_svn has)

   * new python bindings (that don't require pool arguments!)

   * optional text-bases in the working copy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 5 16:25:19 2005