On Wed, Oct 10, 2012 at 11:30 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> It's been a bit since I prodded the community for a status check on
> Subversion 1.8, so here we go.
> Let's start with roadmap.html. We've got several "green lights" on the
> grid. We've got several yellows, too:
> - Improved handling of local moves/renames - looks like we're down to
> multi-layer move issues right now. Is that correct?
> - Editor V2 - Hyrum sez that "the work is sufficiently protected on trunk as
> to be releasable". But I was reminded this morning about the svnrdump
> situation: svnrdump appears to be broken under ra_serf w/ editor v1
> (http://subversion.tigris.org/issues/show_bug.cgi?id=4116). This doesn't
> sound releasable.
I've been somewhat AWOL on this the past few months due to a number of
Real Life factors. While I can't dedicate the amount of time I
previously had, my hope is that I can spend some time looking at this
over the next few days while at Subversion Live.
It may take a bit to page in the state, though. If somebody else
wants to run with it, I'll happily act as a reference.
> - libsvn_ra_serf stabilization - we're making progress here, but there are
> still open issues (such as the aforementioned svnrdump one!)
> - Symmetric merge - Julian has called for review of this work (as well as
> for a new term to describe it). Is anyone doing this?
> - Inherited properties - This is, as far as I know, finished and should be
> shown as such. Paul?
> And then there are all the typical red items. API reviews, performance
> reviews (is anyone really signing up for this?), issue triage (which I will
> probably begin myself soon), etc.
> What else?
> - Paul is working on some of the server-dictated configuration stuff on his
> - Julian has also requested code review of his 'svn mergeinfo' graph display
> 1.7.0 was released a year ago tomorrow. How can we ensure that we aren't
> still asking about the status of 1.8 another six months from now?
Concrete, actionable steps with individual ownership. Not ownership
of code, of course, but somebody who will be accountable for getting X
done for the release.
Received on 2012-10-10 20:30:25 CEST