> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpilato_at_collab.net]
> Sent: woensdag 15 augustus 2012 18:22
> To: Subversion Development
> Subject: Finalizing the definition of 1.8.0
>
> Hello, all.
>
> Echoing in the back of my head are promises we devs have made to avoid
> long
> release cycles, and 1.7.0 recently turned 10 months old. There are a few
> ongoing bits of feature work happening on branches or in various states of
> completion on the trunk, and I'd really like to avoid 1.8.0 remaining a
> moving target for much longer.
>
> Also echoing in my head are recent conversations with some pretty large
> Subversion-using corporate community members who are starting to sense
> that
> it's about time for another Subversion release, but have no idea what such a
> release might contain or when it will ship. It's the common complaint about
> our poor management of outward-bound communication -- a stale
> roadmap.html
> page, no real user-targeting blog or similar info stream, etc.
>
> It's time to make a dedicated push, not so much to release 1.8.0 -- that
> would be premature, I sense -- but to at least better define it.
>
> After I send this mail, I'll take a shot at doing some updates to the
> Release Status portion of roadmap.html. But in the meantime, allow me to
> start the ball rolling with some sound-offs on outstanding
> works-in-progress, hopefully so we as a community can ultimately come to
> an
> agreement about which bodies of effort should be aimed at 1.8.0, and which
> should be deferred.
>
> ==========================================================
> =============
>
> 1.8.0 Issues: Per http://goo.gl/uo0CN, there are currently 21
> "1.8.0"-milestoned (that is, per our convention, 1.8-blocking) issues. Most
> of those are related to...
>
> Serf Stabilization: There's clearly a body of work required here to get
> ra_serf up to snuff for service as our sole HTTP communication library.
>
> Conflict Storage: I get the sense that there was energy invested on this
> for 1.8, possibly culminating in the trunk changes to defer interactive
> conflict handling until the tail end of update/merge operations. Maybe Bert
> or Stefan can update this roadmap.html item?
[It appears I didn't send my original reply, so rephrasing here]
The skel based conflict storage work is complete, but needs a working copy format bump to be enabled. A format bump requires more coordination and the mail thread about that died out some time ago. We should probably plan the bump as part of the process towards 1.8.0.
(Before the bump we can still change the format while after that we need to follow the skel extensibility rules. So more testing of the code is welcome).
Bert
Received on 2012-08-18 12:31:37 CEST