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

Re: fsfs-format7 integration plan

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Mon, 1 Jul 2013 16:42:27 +0400

On Sun, Jun 30, 2013 at 2:48 PM, Stefan Fuhrmann
<stefan.fuhrmann_at_wandisco.com> wrote:
> Hi all,
>
> This is based on what was discussed in Berlin already.
>
> The goal is to get FSFS improvements reviewed & integrated
> into /trunk a.s.a.p. and to bring the code for the new backend
> to /trunk as well and continue development there. So, the
> plan is:
>
> * On the fsfs-format7 branch, duplicate the fsfs-f7 code and
> turn it into a new experimental fs backend. I will name it FSX,
> with "X" standing for "experimental". It pronounce it "fisiks"
> which underlines its design goals.
>
> * Rip out the f7 code from the fsfs backend.
>
> * Open a "fsfs-improvements" integration branch. Merge all fsfs
> relevant changes in there in a hopefully review-friendly way.
>
> * Let people review (give them 2 weeks) & merge the integration
> branch to /trunk.
>
> * Continue work on fsx during that period and merge it directly
> to /trunk once the fsfs-improvements branch got closed.
>
> Everbody fine with that? Comments?
>
I remember we discussed policy about requiring three +1 for merging
branches. I think these fsfs branches is good candidate for this
policy.

It also makes sense to remove any backward compatibility code from
FSX, since it's new FS layer.

-- 
Ivan Zhakov
Received on 2013-07-01 14:43:24 CEST

This is an archived mail posted to the Subversion Dev mailing list.