Messages in this thread | | | From | "Mike Black" <> | Subject | Automating 2.3 patches | Date | Sun, 11 Oct 1998 08:13:47 -0400 |
| |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type> <META content='"MSHTML 4.72.2106.6"' name=GENERATOR> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT color=#000000 size=2>I've got a suggestion to speed up the 2.3 patch cycle.</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>We can still keep the benevolent dictator model (thanks Linus!).</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>What we need to do is speed up the patch testing cycle. This is now being done thru the maillist.</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>Could we put together a web-site that allowed users to vote good/bad on patches against Linux releases? Users would test a patch against a specific release and then post OK or BAD/WHY on the web site.</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>This way, users could determine their own level of need/risk in testing patches. And, Linus could use the statistics to determine when to include a patch in the development kernel (same would be true of the stable kernel too). Anybody could go the web site and look at the stats for any patch to determine.</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2>This way, the anal retentives could say "I am not dowloading a patch until it is 100% safe), the daring would test any patch anyway, and the rest of us would pick some point between.</FONT></DIV> <DIV><FONT color=#000000 size=2></FONT> </DIV> <DIV><FONT color=#000000 size=2><BR>This would put virtually no load on Linus (somebody else would manage the web-site --pretty minimial once it's setup).</FONT></DIV></BODY></HTML>
| |