On Tue, Jul 17, 2007 at 01:56:57PM -0700, Dan Nicholson wrote: > > I'm pretty much in that boat :) I'll be out of town the July 25-30, > but I'll be more than happy to give time when I can. I think we can > pretty much push a package freeze right now and cut a branch. The only > thing I'd be interested in seeing is glibc-2.5.1 if it happens. Also, > I have a couple previously mentioned bootscript patches that I'd like > to push in. Those are low priority, though. > Like everybody else, I'm lacking time. But we do need to get something less-old released. In my case, my limited testing will probably be concentrating on ppc64 for clfs (still trying to find a version of gcc-4.2 which works). And I'm hoping to go on holiday at very short notice. But I can hopefully build a current LFS in the next week (I'd pencilled in a 'bleeding edge' build with gcc-4.2 and glibc-2.6+, but that can wait if we are going to make a release).
I was going to say 'yes' to a package freeze (and if glibc-2.5.1 appears in a timely fashion you can knock me down with the proverbial feather!), except that (a) ISTR you weren't very confident about linux-2.6.21 (you quoted Dave Jones's comments, I think) and indeed Linus found its release somewhat painful, and (b) 2.6.22.1 is out (WFM!) and might last a little bit longer (by the time 6.3 comes out, 2.6.21 is unlikely to still be maintained). What do your bootscript patches do, and how do you view their risk ? ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
