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

Re: Subversion 1.5 Status Update

From: Mark Phippard <markphip_at_gmail.com>
Date: 2007-10-04 19:52:35 CEST

On 10/4/07, Karl Fogel <kfogel@red-bean.com> wrote:
> "Mark Phippard" <markphip@gmail.com> writes:
> > There is definitely some issues in the tracker that anyone could step
> > in and knock off if you want to help. There are also at least a few
> > items being worked on that do not currently have the 1.5 milestone
> > attached, but will likely be done in time for release -- such as
> > relative externals.
> >
> > It is hard to say at this point how we are doing in terms of our goal
> > date of October 12th. [...]
>
> I think we're going to make Oct. 12th, but it would be great if
> someone could do a sweep of the "---" (unmilestoned) issues in the
> tracker. It's usually best if one person does that, so they can spot
> dups quickly, etc.
>
> I'd like to do it, but I feel I'd better work on sparse-directories
> right now... and of course, the closer to Oct. 12th the "---" sweep
> happens, the less able we would be to handle any surprise discoveries.
> So if someone wants to do it now, that'd be great. Otherwise, I'll
> get to it when I can.

I can tentatively volunteer (I'd rather you have more time to help
code). The tentative part is that I am not sure what the job is. I
guess I'd be looking for things that are now DONE with an eye for any
1.5 blockers that we missed? What do I do with everything else
though? Leave at --- or assign to 1.6-consider or what?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 4 19:52:45 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.