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

Re: Branching 1.6 this week? (no, next week)

From: Mark Eichin <eichin_at_gmail.com>
Date: Tue, 4 Nov 2008 16:49:47 -0500

http://svn.haxx.se/dev/archive-2008-10/1170.shtml has the description,
suggested patch, and attached script to reproduce the problem by
creating a repository and doing some simple merges (subject: svn
mergeinfo bug with script to reproduce it (finally)! (was Re: empty
mergeinfo produced by svn_mergeinfo_inheritable))

As far as release definitions go, I'd actually want to see it go in
1.5.5 (since it breaks merges and was introduced in 1.5.0), but I
haven't gotten any responses (beyond another end user reporting that
they see the problem too...)

On Tue, Nov 4, 2008 at 3:51 PM, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> Mark Eichin wrote:
>> Does that suggest that the "empty revision range" fix could get
>> included in 1.6, if I could get some one to look at it in the next
>> week?
>
> I'm not familiar with the specific fix you are referring to, but the basic gist
> of what gets into a release and what doesn't can be found here:
> http://subversion.tigris.org/hacking.html#release-numbering
>
> Has the patch you refer to already been committed to trunk?
>
> -Hyrum
>
>> On Tue, Nov 4, 2008 at 9:46 AM, Hyrum K. Wright
>> <hyrum_wright_at_mail.utexas.edu> wrote:
>>> Karl Fogel wrote:
>>>> "Hyrum K. Wright" <hyrum_wright_at_mail.utexas.edu> writes:
>>>>> The current plan is to branch Nov. 5, this Wednesday, two days away. I'm
>>>>> currently not very optimistic that we are going to make that date, for the
>>>>> following reasons:
>>>>>
>>>>> * Loads of stuff in TODO-1.6
>>>>> * Buildbot lit up like a Christmas tree (I can reproduce the 8 failing tests
>>>>> locally, too.)
>>>>> * A large number of XFAIL tests on trunk, mostly merge tests.
>>>>> * A general feeling that despite our best efforts, another week may be needed.
>>>>>
>>>>> I'm not heavily involved in much of the above (though I do plan on looking at
>>>>> the FSFS problems in TODO-1.6), so I can't comment on whether they are minor
>>>>> issues or will need extra time. As mentioned before, I'm willing to push back
>>>>> the branch date a bit, but I feel a bit uneasy about going beyond Nov. 12.
>>>>>
>>>>> Thoughts?
>>>> I think Nov. 12th would be great. I don't know about other U.S. devs,
>>>> but the election has certainly been a factor for me this week (was out
>>>> in Pennsylvania doing Obama canvassing, for example).
>>>>
>>>> The issue-2843-dev branch merge has been going okay. When I saw a bunch
>>>> of test failures on the branch, after bringing it up-to-date with trunk,
>>>> I worried it might be really broken. But now that I'm testing trunk I
>>>> think those test failures are probably actually from trunk, not the
>>>> branch. How, um, reassuring :-).
>>> Yeah, I think these concerns justify pushing the date back, as much as I hate to
>>> do it.
>>>
>>> New official branch date: Nov. 12.
>>>
>>> -Hyrum
>>>
>>>
>>
>>
>>
>
>
>

-- 
_Mark_ <eichin_at_thok.org> <eichin_at_gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-04 22:50:01 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.