Subversion 1.8 -- where are we?

["C. Michael Pilato" <cm...@collab.net>]

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 <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Re: Subversion 1.8 -- where are we?

[Stefan Sperling <st...@elego.de>]

On Wed, Oct 10, 2012 at 11:30:22AM -0400, C. Michael Pilato wrote:
> - Improved handling of local moves/renames -  looks like we're down to
> multi-layer move issues right now.  Is that correct?

Well... sort of. I've already fixed the way mived-rev moves are
represented in the DB schema, and also disallowed mixed-rev
moves from happening by default. This gets is somewhere close
to having the multi-layer move issues done.

However! While we're finally storing move information correctly (at
least in terms of the current state of the art), we're not actually
*using* it for anything yet!

All behavioural changes I had implemented on top of the old moves
storage code, which was broken for multi-layer cases, have been reverted.
So if we release move support in its current state it won't buy our
users much and we might as well not bother shipping this feature.

So I'd like to improve handling of some tree conflicts involving moves
before release. At the rate we're currently going (and with prospected
schedule at $JOB) I suspect that this won't be done before December.

If the community decides that this is taking too much time I won't
complain and work towards 1.9. After all, I started working on this
before 1.7.0 was even released, so I've certainly spent a lot of
time on this as it is. And there are other nice new features queued up
which I wouldn't want to hold back for this. But I would be happier
to release 1.8 with at least some behavioural improvements around
conflicts involving moves.

A recent IRC discussion between me and Philip about what's still
needed starts here:
  http://colabti.org/irclogger/irclogger_log/svn-dev?date=2012-10-08#l175
It starts a bit earlier actually but it's quite long. If you'd like to
read the entire thing please scroll up a bit.

Re: Subversion 1.8 -- where are we?

[Hyrum K Wright <hy...@hyrumwright.org>]

On Wed, Oct 10, 2012 at 11:30 AM, C. Michael Pilato <cm...@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
> 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?

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.

-Hyrum

Re: Subversion 1.8 -- where are we?

[Paul Burba <pt...@gmail.com>]

On Wed, Oct 10, 2012 at 11:30 AM, C. Michael Pilato <cm...@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.
>
> - 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?

It's completed, I updated the roadmap.

> 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).

Just one branch, ^/subversion/branches/auto-props-sdc.  The autoprops
work is done, starting in on "global-ignores".  This should be ready
for review shortly, a week or two at worst.

-- 
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba

> - 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 <cm...@collab.net>
> CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development