On Tue, 2005-12-06 at 22:14 +1100, James Rayner wrote: > @ PHP5.1 > To most people a point release like that is a minor upgrade. Its not > the Arch Dev's fault it was broken.
If you just see numbers, this a problem I think... Minor numbers are 5.1.x for php .. and when you maintain a package and see that it could break smth (it's on php website), you have to pay attention... > > @ Communication. > Arch has a homepage which communicates upcoming things like hwdetect and > initrd. Yes after the release. Communication should be before the release to help transition, tests... Not after... It's more easy to prepare than to repair. > > @ Arch in production > Arch wasnt ever made for production, and i wouldnt use it for that. I > wouldnt even reccomend it for that. Arch is for the sorta person who > would want to get that PHP5.1 update straight away, without testing, > and then downgrade if needed. Sometimes you couldn't downgrade when your machine was down. And found the previous package isn't so easy for people that don't know the de mirror... Arch could be a very good distribution in production, that's too bad :( > > If you're unsure about a major release on a production system that > cant handle a break, wait a few days, let others test it, thats what I > did back when udev was still a finicky thing with problems with every > second release. > You're a lucky guy... and what about people that just install their distribution ? And what about updates of packages done whe you install other.... All these points should be taken in consideration.... > Arch has a good setup now, with good communication. There is a > homepage, there is the forums, there is the mailing list. All have > info about upcoming major changes. And I think theres also the > newsletter. Oh and the Dev blog too. Sure we have info. Bu you know, sometimes you are very urged at work and don't have time to look in forums, ml, google, you just want it works. When your machine is down and you have to reinstall it, it would be a pleasure not to be faced to such problems.... bleeding edge isn't breaking edge... Oh btw, communication is better when you inform before than after... But I already said it. > > James Rayner > > -- > iphitus - archck maintainer, arch trusted user. > Home:iphitus.loudas.com > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
