Re: Using Lenny on production server?
Neil Gunton wrote:
I run a moderately busy community website, hosted on my own LAMP (Perl,
MySQL) AMD64 server, currently running Etch in a colo. I am going to go
up to the datacenter on July 16th to rebuild the server for various
reasons. This will include a complete re-install. One change I am
considering is to upgrade to Lenny. I've read that Lenny will shortly be
frozen, for possible release in September 2008, so I'm thinking that it
must be fairly "stable" (not in the formal sense, of course) at this point.
Upheavals, no, bugs, mmmm... A freeze normally comes quite a long time
before release. A quick look here:
I know the conventional wisdom is to only install Stable on servers;
however I am wondering if I can temper that view with the current state
of Lenny (almost ready for move to stable) and just install it now
rather than go through a dist-upgrade later.
So: What do people think about the wisdom of running a clean install of
Lenny in a production server environment at this time? I am not a bank,
I don't need five-nines uptime, but I would just like to know if the
system is generally fairly stable and "probably" not prone to any major
upheavals at this point. Any insights there?
suggests to me that Lenny is at least a year away from release,
possibly 18 months going by previous releases. Remember that Etch is
only a few months old as Stable.
I hadn't looked at this page since the last release, when the third line
was added. I do find it a little odd that Etch seems to have twice as
many bugs deemed release-critical as Lenny, though a quick glance
through them suggests that only a small proportion are likely to trouble
a small private server running on i86-32.