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

Subversion 1.8 -- where are we?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 10 Oct 2012 11:30:22 -0400

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.

- 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
branch(es).

- Julian has also requested code review of his 'svn mergeinfo' graph display
stuff.

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?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2012-10-10 17:30:56 CEST

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.