Tim Cutts <[EMAIL PROTECTED]> wrote: > > Seriously. There's just no way you're going to change the way Debian > > makes releases, or rather, doesn't. It's too big, and there are just > > too damn many people involved, many of whom simply don't care about > > releases. As long as we maintain our current release criteria (which I > > don't necessarily think we should change) we will get slower and slower > > as we get bigger and bigger. > Which is a rather clear sign that the way Debian makes releases has outgrown its usefulness.
> Which could be seen as a problem by some; but in some ways it's > probably the way to go. As far as my own use of Debian goes, almost > every machine I install runs testing, and has done for years. There's > a level of protection in there thanks to the rules that are in place, > and I rather like the incremental improvement approach as opposed to > release-based. > Me too, but it might be completely different if you do it for business critical systems. > With the trend as it is at the moment, the endpoint is that Debian will > eventually stop releasing altogether (some end users probably think > this has already happened!) and will essentially become an upstream, > developer-oriented, steadily evolving distribution from which the likes > of Ubuntu take regular snapshots for the masses to use. > Stopping releasing might be a good idea but there should be a better way. IMO the problem is the stable release isn't updated on a regulare basis. It might be a better idea to divide Debian into subsystems which could be released much faster when needed. O. Wyss -- Development of frame buffer drivers: http://linux-fbdev.sf.net Sample code snippets for wxWidgets: http://wxcode.sf.net How to build well-designed applications: http://wxguide.sf.net Desktop with a consistent look and feel: http://wyodesktop.sf.net
