-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 By example i will use the biggest Brazilian Fedora Case. SERPRO (Brazilian Government IT Department) has more than 8.000 desktop stations and several servers using Fedora inside spread in 26 Brazilian States. Do you have any idea of what i'm talking about ???? How can they update it every six month?? It's a craziness !! It involves planning and a lot of work! it's not that simple!!!!! IMHO the release and life cycle must be increased! RELEASE -> 1 per year LIFE CYCLE -> 2 years It'd reduce the Artwork, Free Media, Marketing, Translation, Documentation and Packing issues. .... and mirrors, band use and others things!!!!!!!!!! Best regards! Rodrigo Padula de Oliveira Gian Paolo Mureddu escreveu: > Greg DeKoenigsberg escribió: >> >> IMHO, it's far more interesting -- and useful -- to make upgrades work >> flawlessly. >> >> --g >> > > > I couldn't agree more with you on this! Theoretically upgrades shouldn't > need to be too difficult, heck you can sort of do them "by hand" if you > know what files you need and more specifically, what /parts/ of the > files are needed... I'm specifically talking about passwd, shadow, group > & gshadow, and paths such as /home, /root, etc. Of course there's also > the "individual applications' config files, which can still be worked > out. I've been thinking about this and it shouldn't be too difficult, > but have been told time and time again that such a feat is impractical > and nonsensical in the long run. I'm not convinced, but, then again it > could be made possible for an automatic upgrade process to also be clean > enough... I'll give it a bit more thought and maybe post an RFE on > Bgzilla about the issue. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHHSWtPg3HAC1vlg4RAgNJAJoD9ulktv1IFbej0mafvHdxxgcZEwCbBkBA OqO1pmAwzKEsKS0v+25HonQ= =FQbb -----END PGP SIGNATURE----- -- Fedora-marketing-list mailing list Fedora-marketing-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-marketing-list
