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

Re: Let's set a date/goal for the 1.5 Branch

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-08-31 20:18:01 CEST

"Ivan Zhakov" <chemodax@gmail.com> writes:
>> > In addition to merge tracking and sparse-directories I want to see
>> > following stuff in Subversion 1.5:
>> > 1. Remove dependency of apr-iconv on Windows
>> > Status: Finished, only one cosmetic to be done (don't copy libapriconv if
>> > libaprutil configured without it)
>> > 2. Passing all test suite using serf.
>> > Status: There are only several tests failing, but it looks that
>> > they have one reason.
>> > 3. SSPI authentication in serf
>> > Status: Initial implementation is available in branch, but it still
>> > have problems.
>> >
>> > So October 12th looks reasonable date for branching. Please note that
>> > I don't know status of merge-tracking and sparse directories stuff.
>> >
>> > I'm going to finish (1) and (2). And focus on (3) after that.
>>
> Did we change policy to use issuezilla for *all* tasks? (1) looks too
> small for filling. (2) have failling tests, so I think it doesn't
> need issue too. Probably (3) have to be filed.
> Correct me please, if I misunderstand our process. And we have policy
> to create issues for all tasks as possible.

I think we're just using the tracker so we have one source for knowing
how we're doing on 1.5. I agree with your assessments: (1) is too
trivial (though it would also be okay to have an issue for it), (2) is
a test suite failure so it's in our face all the time anyway, and (3)
is issue material.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 31 20:15:05 2007

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.