[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Finalizing what's in 1.5

From: Branko ─îibej <brane_at_xbc.nu>
Date: Thu, 10 Jan 2008 22:36:29 +0100

Ben Collins-Sussman wrote:
> On Jan 10, 2008 1:04 PM, Blair Zajac <blair_at_orcaware.com> wrote:
>
>
>> Now after reading the IRC conversation, it appears that the amount of energy
>> going into #2897 isn't going to be enough for a faster 1.5 release, there's
>> nobody else really looking at the work. So if we want this feature, we should
>> merge it soon into trunk and deal with it in trunk.
>>
>
> That's an interesting question: is the branch so unstable (at the
> moment) that would make the trunk impossible to work on? If not,
> there's no reason for the branch to persist.
>
> My vote is the same always (which doesn't have much weight, since I'm
> not doing any work): Kamesh's branch is THE main use-case for
> merge-tracking and svnmerge.py. An svn 1.5 release without the
> ability to track and painlessly re-merge feature branches just isn't
> interesting to the general public.
>

+1. I won't repeat earlier rants, since the most you'll get in return is
lots of cheering and no code ... in the short term. :)

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-10 22:37:08 CET

This is an archived mail posted to the Subversion Dev mailing list.