Aaron Griffin <[EMAIL PROTECTED]>: >b) As for Arch in production environments - Arch provides the perfect >framework for production environments if you make sure to manage your >own repo, and have a single test machine for official packages. It\'s >not hard, and many many businesses test upgrades anyway. I know of no >one who just downloads new versions of programs on their production >machines on a whim - there\'s always a decent amount of testing.
I agree with this. The only thing we should keep in mind is... the time. For me a perfect distro for a production enviroment is when you spend 20% of the time for maintenance (upgrades, configuration etc.) and 80% for actually using it to do your job :-) (like in the famous pareto rule). >d) As for the notification "channel", I see things like: >"How about the front page?" - "Not everyone checks the front page" >"Well, then, how about an RSS feed?" - "Not everyone has a feed reader" >"How about forums/mailing list?" - "Not everyone reads those" >Christ people, pick one. There will never ever be one medium which >satisfies everyone. The devs have chosen to use the dev blog, which >Jason so kindly linked to. If someone doesn\'t like this, then tough >shit - deal with it. How about doing it in a KISS way: replace front page news content with excerpts from the dev blog (first 3 lines of the last 5 posts or something like this) ? Correct me if I'm wrong but putting content into dev blog is easier than putting it into the news. Plus the dev blog already has rss channels and comments from users not mentioning the search feature. It would also be better IMO to have one system less to maintain. -- Rafal Szczepaniak (Lanrat) _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
