On Fri, 2005-05-20 at 17:24 +0200, Cimmo wrote: > Dan Williams ha scritto: > > >You must balance the stability of software you ship with the features > >the software provides. During development, if you are working with beta > >software, you identify bad bugs and you fix those before you ship. You > >don't wait for upstream to fix them because upstream is not shipping > >Fedora Core and upstream frankly doesn't care about Fedora Core. It's a > >tradeoff; if you never trade something off, you never ship anything, or > >you ship crap that nobody wants to use because its very old. > > > > > There is an alternative option: > give OOo 1.1.4 when FC4 will be released, and when OOo 2.0 will come out > give it like other updates. That doesn't work well, because then you _completely_ change the way people work after the project has come out. If you download Fedora Core 4, you expect that it more or less works the same way forever. If you upgrade OOo to 2.0, then that's a completely different program with a huge number of changes and that's not good. Things which used to work may now fail. Menu items are no longer in the same place, etc. Things can be unstable during development, but after a release you work to fix bugs and improve stability, not dump a huge new unknown package on people. Dan