From: "Rogelio M. Serrano Jr." <rogelio@smsglobal.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Adrian Bunk <bunk@kernel.org>
Subject: Re: [poll] Is the megafreeze development model broken?
Date: Tue, 13 Nov 2007 02:25:15 +0800 [thread overview]
Message-ID: <47389A8B.7070405@smsglobal.net> (raw)
In-Reply-To: <20071112171456.GN9771@stusta.de>
[-- Attachment #1.1: Type: text/plain, Size: 1450 bytes --]
Adrian Bunk wrote:
>>
>> The core libc and supporting libraries is the core. and the toolchain
>> the core dev. Those can be updated twice or even once a year. The kernel
>> can be updated once a month if you like.
>>
>
> A new release of the Linux kernel has more than half a million lines of
> code changed. If you do any estimates based on how many lines of changed
> code equal one newly introduced bug you see the problem...
>
> And the difference between an upstream kernel and a distribution kernel
> are 3-6 months of testing and bugfixing.
>
>
True. But the libc and toolchain dont need to be as "dynamic".
>> I stopped using debian myself and used DIY linux based toolchain and
>> libc. Thats the stable core that i have been using for 4 months. If
>> debian can reduce the footprint of the "stable core" and do monthly
>> releases of package bundles i will use it again.
>>
>
> Geeks like you and me want the latest software
> (I'm using Debian unstable/testing).
>
> But most users want a Linux installation that simply works - and this
> includes all software on the system at all times.
>
Yeah me too. Sidux and mepis does not do megafreezes. I think whats
needed is to build and test groups of packages that work closely
together and release them frequently as a group.
> cu
> Adrian
>
>
--
Democracy is about two wolves and a sheep deciding what to eat for dinner.
[-- Attachment #1.2: rogelio.vcf --]
[-- Type: text/x-vcard, Size: 333 bytes --]
begin:vcard
fn:Rogelio M. Serrano Jr
n:M. Serrano Jr;Rogelio
org:SMSG Communications Philippines;Technical Department
adr:;;;;;;Republic of the Philippines
email;internet:rogelio@smsglobal.net
title:Programmer
tel;work:+6327534145
tel;home:+6329527026
tel;cell:+639209202267
x-mozilla-html:FALSE
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-11-12 18:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:56 [poll] Is the megafreeze development model broken? ciol
2007-11-07 23:06 ` Rik van Riel
2007-11-07 23:11 ` ciol
2007-11-08 1:36 ` Adrian Bunk
2007-11-08 20:45 ` ciol
2007-11-08 6:18 ` Stephen Hemminger
2007-11-08 13:38 ` David Newall
2007-11-08 14:26 ` Chris Snook
2007-11-08 20:41 ` ciol
2007-11-09 0:15 ` Chris Snook
2007-11-12 11:09 ` Eric W. Biederman
2007-11-12 13:51 ` Tuomo Valkonen
2007-11-12 15:20 ` Adrian Bunk
2007-11-12 16:02 ` Tuomo Valkonen
2007-11-12 16:56 ` Adrian Bunk
2007-11-12 17:16 ` Tuomo Valkonen
2007-11-12 17:34 ` Adrian Bunk
2007-11-12 17:42 ` Tuomo Valkonen
2007-11-13 10:11 ` David Newall
2007-11-12 17:37 ` Rogelio M. Serrano Jr.
2007-11-12 17:53 ` Tuomo Valkonen
2007-11-13 12:28 ` Radoslaw Szkodzinski
2007-11-13 13:09 ` Tuomo Valkonen
2007-11-12 16:13 ` Rogelio M. Serrano Jr.
2007-11-12 17:14 ` Adrian Bunk
2007-11-12 17:18 ` Tuomo Valkonen
2007-11-12 23:39 ` Matthias Schniedermeyer
2007-11-13 0:12 ` Tuomo Valkonen
2007-11-12 17:30 ` david
2007-11-12 18:25 ` Rogelio M. Serrano Jr. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47389A8B.7070405@smsglobal.net \
--to=rogelio@smsglobal.net \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox