On Sun, 2005-12-11 at 16:07 +0100, Jakub Bogusz wrote: > On Sun, Dec 11, 2005 at 03:54:20PM +0100, [EMAIL PROTECTED] wrote: > > Dnia Sun, 11 Dec 2005 14:52:49 +0100, Adam Gołębiowski > > <[EMAIL PROTECTED]> napisał: > > > > > On Sun, Dec 11, 2005 at 02:45:22PM +0100, Marcin Król wrote: > > >> 1) Maintain my machines, by simply doing poldek --upgrade-dist out of > > >> stable tree. Occasionally there will be need to do some manual upgrades > > >> like from postgres 8.0 to 8.1 which requires database dump/restore. Now > > >> lets assume that we will stay with current distro politics + we will > > >> release new version every year. So once a year I'll probably have to > > >> reinstall all the machines because version Z was released and X has > > >> reached an EOL. > > > > All of that is true - as long as from time to time we'll bake some iso, > > everything is fine for me. > > > > > > What about some groundbraking change like gcc update (breaking BC)? > > > > That'd be a point to make an iso - perfect for making some 'version', > > 'release', 'snapshot' or whatever You call it - an iso. > > And what can I do with ISO full of security holes (or other serious > bugs), with only binary-incompatible updates on ftp? > > "always in development" works good only for periods of time limited by > "big transitions".
Maybe "medium transitions" with less time between could be possible? C++ ABI breakage is the biggest I can think of. Otherwise, major transitions are relatively small. _______________________________________________ pld-devel-en mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
