linux-ext4 - Re: [RFC] Btrfs mainline plans

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 7 Oct 2008 23:25:39 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Chris Mason <chris.mason@...cle.com>
Cc:	"Serge E. Hallyn" <serue@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org, Theodore Tso <tytso@....edu>
Subject: Re: [RFC] Btrfs mainline plans

On Tue, Oct 07, 2008 at 12:01:24PM -0400, Chris Mason wrote:
> On Tue, 2008-10-07 at 18:27 +0300, Adrian Bunk wrote:
> > On Mon, Oct 06, 2008 at 09:40:03AM -0400, Chris Mason wrote:
> >  
> > > 
> > > The btrfs timelines have always been aggressive, and as btrfs gets
> > > closer to feature complete, the testing matrix grows dramatically.  I
> > > can't promise my crazy timelines won't slip, but I've been hacking away
> > > in the basement for almost 18 months now and it's time for me to get off
> > > the pot and make it stable.
> > > 
> > > Ext4 has always had to deal with the ghost of ext3.  Both from a
> > > compatibility point of view and everyone's expectations of stability.  I
> > > believe that most of us underestimated how difficult it would be to move
> > > ext4 forward.
> > > 
> > > Btrfs is different for lots of reasons, and being in mainline will
> > > definitely increase the pressure on the btrfs developers to finish, and
> > > the resources available for us to finish with.
> > 
> > Your last sentence does not make sense:
> > 
> > According to your timeline btrfs 1.0 will be released in Q408 [1] - and
> > the merge window for 2.6.29 will be in Q109.
> 
> Planning for mainline inclusion is always a guessing game.

The 2.6.29 merge window will start in January - everything else is much
more unlikely than an incompetent chick from Alaska getting only one 
heart attack away from the big red button.

> Cutting 1.0
> is different from being in mainline, and the dates don't have to be the
> same.

Sure, but Andrew's "special-case treatment" suggestion does not apply if 
1.0 gets released before the 2.6.29 merge window.

>...
> -chris

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html