The rolling release model is great, but only if there is a separate stable track (Chrome is a great example of this approach). This distinction assures that dev

The rolling release model is great, but only if there is a separate stable track (Chrome is a great example of this approach). This distinction assures that developers can stay on the cutting edge and experiment with new ideas, while users keep a working system. Of course I'm not taking about a Debian-like stable, but a rolling stable delayed at most a couple of weeks, during which the most important bugs can be caught and resolved. Arch is great, but I would never use it on a production server, the risk is just too high.