On 8/31/07, Daniel Rall <email@example.com> wrote:
> On Fri, 31 Aug 2007, Ivan Zhakov wrote:
> > On 8/31/07, Mark Phippard <firstname.lastname@example.org> wrote:
> > > On 8/30/07, Karl Fogel <email@example.com> wrote:
> > > > "Mark Phippard" <firstname.lastname@example.org> writes:
> > > > > I propose October 12th as that date, which gives us 6 full weeks of
> > > > > development time, and if we get the pieces in place quickly for a
> > > > > release candidate, gives us enough time to get the GA out before the
> > > > > end of the year. Personally, I think we should shoot for end of
> > > > > November, so that X-Mas and holiday season does not get in the way.
> > > >
> > > > +1
> > > >
> > > > I think it's time to set a date and mean it. We've got to get this
> > > > thing out before the end of the year!
> > >
> > > Thanks for responding. I thought this would have got more responses
> > > than it has.
> > >
> > > Hyrum, Erik, Vlad, Ivan, Eric, Blair ???
> > 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.
> Do these have corresponding issues in the tracker yet? If not, I
> volunteer to file them.
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.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Aug 31 20:04:15 2007